Skip to content

DOCS: Explain Bunny CNAME/ALIAS behavior.#4368

Open
jfexyz wants to merge 3 commits into
DNSControl:mainfrom
jfexyz:bunny_dns_cname_alias_docs
Open

DOCS: Explain Bunny CNAME/ALIAS behavior.#4368
jfexyz wants to merge 3 commits into
DNSControl:mainfrom
jfexyz:bunny_dns_cname_alias_docs

Conversation

@jfexyz

@jfexyz jfexyz commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Just an addition to explain that while Bunny DNS allows root CNAMEs, here in DNSControl, you should use ALIAS and the CNAME will result. This was initially unclear to me when setting up DNSControl.

Comment thread documentation/provider/bunnydns.md Outdated
Comment on lines +52 to +53
Bunny supports adding CNAME records for the root domain (`@`), but within
DNSControl the `ALIAS` record should be used.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I think this needs a little more explanation. Something like:

Bunny supports adding CNAME records for the root domain (@). Use the ALIAS record type and DNSControl will generate a CNAME as appropriate.

D("example.com", REG_NONE, DnsProvider(DSP_BUNNY_DNS),
A("test", "1.2.3.4"),
);
D('example.com', REG_NONE, DnsProvider(DSP_BUNNY_DNS), A('test', '1.2.3.4'));

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

JavaScript code should use double quotes (") for strings, not single quotes (').

See https://docs.dnscontrol.org/developer-info/styleguide-doc

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Ok, y'all have a .prettierrc file that says otherwise. Which is why this PR is so huge... you have your repo set up to use Prettier, but don't actually seem to be using it properly. Hence me having to spend time disabling and working around this. I'll probably just drop wanting to get this merged, tbh. When y'all figure out your systems set up, I'm happy to take another crack at it.

@TomOnTime TomOnTime Jun 9, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Ah, that's certainly a contradiction! We use prettier for pkg/js/helpers.js and nothing else. We should update the style guide (or maybe change pkg/js/helpers.js to be the same as the docs?). CC @cafferata for his opinion.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Or use a .prettierignore file to ignore the docs. Or ideally just use Prettier for the docs (you can have a separate .prettierrc in the docs dir with different settings) and eliminate all the bikeshedding...

To be clear, the huge problem right now is that because you have that .prettierrc file, Zed and VS Code and any other editor set up to respect them will reformat everything in a file when you make edits.

Comment on lines +108 to +109
You can configure Bunny's Pull Zone type with `BUNNY_DNS_PZ`. The target is the
Pull Zone ID:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
You can configure Bunny's Pull Zone type with `BUNNY_DNS_PZ`. The target is the
Pull Zone ID:
You can configure Bunny's Pull Zone type with `BUNNY_DNS_PZ`. The target is the Pull Zone ID:

CC @cafferata Is it ok that these lines are being broken? I believe you recently unbroke lines.

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

Development

Successfully merging this pull request may close these issues.

3 participants