Skip to content

CHORE: DNSControl.org zone/zone transfer to TransIP#4204

Open
cafferata wants to merge 1 commit intoDNSControl:mainfrom
cafferata:dnscontrol.org-transfer
Open

CHORE: DNSControl.org zone/zone transfer to TransIP#4204
cafferata wants to merge 1 commit intoDNSControl:mainfrom
cafferata:dnscontrol.org-transfer

Conversation

@cafferata
Copy link
Copy Markdown
Member

Initial zone configuration for dnscontrol.org, based on the records provided by @TomOnTime.

Records

  • ALIAS @stackexchange.github.io.
  • CNAME docsdb3053e25d-hosting.gitbook.io.
  • CNAME wwwdnscontrol.org.
  • TXT @ Google Search Console verification
  • SPF_NONE (domain does not send email)

Notes: The zone is staged ahead of the domain transfer. Nameservers will be pointed to the new registrar (TransIP) once Stack completes the transfer.

@cafferata cafferata changed the title CHORE: DNSControl.org zone/zone transfer to TransIP. CHORE: DNSControl.org zone/zone transfer to TransIP Apr 26, 2026
Copy link
Copy Markdown
Collaborator

@TomOnTime TomOnTime left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the general idea of this but not the implementation.

  • nitpick: D_EXTEND is very slow. I don't want to encourage its use.
  • blocker: One domain per file is good. Individual files for spf, google site verification, etc. is better done as macros.
  • needs more discussion: I strongly feel this should be in a separate repo. The domain is not part of the project. For example, if someone were to fork the project, I wouldn't want them to have to delete this and replace it with their own domain.

I think this needs a lot more discussion: I think what we're doing here is trying to decide what "best practice" we want to normalize for our users. I could be talked out of it, but my vision is two parts: (1) provide dnscontrol init (which I haven't tried yet) to help people get started, (2) provide a repo that shows the result of dnscontrol init so that (a) people can see what the result looks like, (b) people can see a working example that is exactly what we recommend, (c) people that don't want to or can't use init can clone this repo as an alternative way of getting started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants