DNS provider request: Site.nl
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 15/100
調査の方向性
Start in records.json to see how existing provider blocks are structured, then read the provider checklist in CONTRIBUTING.md. The new block cannot be finished from the issue alone: the field labels, SRV layout and TXT quoting need live screenshots of the Site.nl add-record form, which a newcomer probably cannot access. Done means a reviewed block with UNVERIFIED prefixes where labels are unconfirmed, plus the README, release notes and tests.
索引モデルが issue の本文から書いたものです。
説明
Summary
Add Site.nl as a provider in records.json, so that --provider site-nl (CLI) and the "Show fixes for" dropdown (web) print the fix instructions for its panel.
Site.nl has no public documentation of its DNS record editor. The helpdesk explains how to open the editor, but it does not give the field labels, the record types, or the formatting rules. We need screenshots of the live add-record form before we can write the four blocks (MX, SRV, TXT, CNAME).
What the public docs say
Source: Hoe beheer je de DNS-records van je domeinnaam (Dutch).
- Menu path: Dashboard → click the domain name in the left sidebar → Domeininstellingen (Domain settings) → Geavanceerde instellingen (Advanced settings). The DNS record editor is there.
- Default settings must be turned off first. While "Gebruik Site.nl standaardinstellingen" (Use Site.nl default settings) is on, Site.nl manages the records itself. The user must turn it off to edit records, and after that the user is responsible for all records. Every block header needs to say this.
- Domains registered elsewhere: add the domain as an external domain, then click the yellow button in Geavanceerde instellingen that points the domain to the Site.nl nameservers. Only after that, change the nameservers at the registrar. The article warns that DNS does not work if the order is reversed. Related: Externe domeinnamen toevoegen aan je Site.nl dashboard, Kan ik mijn domeinnaam koppelen aan een externe DNS, webhosting of server?.
- Rollback: the DNS editor has a revert option with a list of earlier versions and timestamps. Worth a mention in the headers.
- MX hint (sister site Site.eu): How to Add MX Records shows MX values as
10 spamfilter1.site.euand says that a value without the priority gives an error on save. This suggests that the priority goes into the same value field (thebunnypattern,{match}), not a separate Priority field. Unconfirmed. - SPF (Site.eu): SPF records says that SPF is a plain TXT record and that a domain can have only one. Site.eu creates an SPF record automatically for its own hosted email, so a Thundermail user must replace that record, not add a second one.
- Support: [email protected] or the site chat (reply within 24 hours).
No public docs mention SRV or CNAME records.
Infrastructure
Site.nl, Site.eu, Site.de, Site.fr, Site.es and Site.be appear to be one group. site.nl itself is delegated to ns1.site.eu, ns2.site.nl, ns3.site.be and ns4.site.de. To query a Site.nl-hosted zone authoritatively, first check the delegation with dig NS <domain>, then run:
uv run verify_thundermail_dns.py <domain> --resolver ns1.site.eu
What we need (open questions)
- Screenshots of the add-record form in the Site.nl DNS editor, one for each type: MX, SRV, TXT, CNAME. These settle the field labels.
- Is SRV supported at all? If the panel has no SRV type, the SRV block routes the user to [email protected], like
cosmotown. - SRV layout: one combined Host field (
_jmap._tcp) or split Service/Protocol fields? Separate Priority/Weight/Port/Target fields, or one value? - Apex host:
@, blank, or the full domain? - Trailing dots: does the panel append the domain to a target without a trailing dot (
ovh/digitalocean), or store it as entered? - TXT quoting: does the panel add the quotes itself, or must the user type them (
cloudflare)? - Language: is the panel Dutch only? If so, emit Dutch labels with an English gloss, like
metanet-plesk. - Provider key:
site-nl, or a more generalsiteif Site.eu/.de/.be use the same panel? - Verify target: a Site.nl-hosted zone to run end-to-end against. Use a placeholder such as
sitenl.example.comin the repo, never the customer domain.
Plan
Ship with the UNVERIFIED — header prefix for any type whose labels are not confirmed from a live screenshot, as for the other providers. Follow the provider checklist in CONTRIBUTING.md: records.json block, README provider list, release notes (.md and .html), and tests.
- 主要言語
- HTML
- スター
- 3
- フォーク
- 0
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
thunderbird/dns-scripts のほかの issue
-
Optional Recordsオープン
難易度 4/5 3〜5日 初心者へのやさしさ 30/100
thunderbird/dns-scripts#28 ·
-
難易度 3/5 半日 初心者へのやさしさ 45/100
thunderbird/dns-scripts#25 ·
-
Handle CNAME and A record co-existence for MX records対応中かも @rtanglao が 23 日前に担当しました。 オープン
thunderbird/dns-scripts#22 · コメント 1 件 · 担当者 1 名 ·
-
難易度 3/5 1〜2日 初心者へのやさしさ 65/100
thunderbird/dns-scripts#20 ·
-
難易度 5/5 1週間以上 初心者へのやさしさ 42/100
thunderbird/dns-scripts#13 ·
thunderbird/dns-scripts の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 64/100
docker/sbx-releases#737 ·
-
github_actions
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
collective/icalendar#2003 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
area: client bug
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
OCIRepository: pick the Helm chart layer automatically when the first layer is a provenance fileオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
fluxcd/source-controller#2198 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 86/100
zerocracy/judges-action#2848 ·
メンテナーはふだん 1 日以内に返信