Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

DNS provider request: Site.nl

Đang mở
  • Có gì không ổn?
#24 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Chưa có ai nhận issue này.

Đánh giá

Độ khó
4/5
Thời gian dự kiến
3-5 ngày
Mức phù hợp với người mới
15/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
json, markdown, python
Lĩnh vực
devops

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

enhancement

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.eu and says that a value without the priority gives an error on save. This suggests that the priority goes into the same value field (the bunny pattern, {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)

  1. 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.
  2. Is SRV supported at all? If the panel has no SRV type, the SRV block routes the user to [email protected], like cosmotown.
  3. SRV layout: one combined Host field (_jmap._tcp) or split Service/Protocol fields? Separate Priority/Weight/Port/Target fields, or one value?
  4. Apex host: @, blank, or the full domain?
  5. Trailing dots: does the panel append the domain to a target without a trailing dot (ovh/digitalocean), or store it as entered?
  6. TXT quoting: does the panel add the quotes itself, or must the user type them (cloudflare)?
  7. Language: is the panel Dutch only? If so, emit Dutch labels with an English gloss, like metanet-plesk.
  8. Provider key: site-nl, or a more general site if Site.eu/.de/.be use the same panel?
  9. Verify target: a Site.nl-hosted zone to run end-to-end against. Use a placeholder such as sitenl.example.com in 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.

Ngôn ngữ chính
HTML
Star
3
Fork
0
Không có pull request nào được merge trong 30 ngày

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của thunderbird/dns-scripts

Tất cả issue của thunderbird/dns-scripts

Issue tương tự

Thêm issue về DevOps

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.