Skip to content

CNR: Update docs with proper Nameserver example #3592

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 1, 2025

Conversation

mejofi
Copy link
Contributor

@mejofi mejofi commented May 31, 2025

'NAMESERVER' values should be specified with a trailing dot, and, according to the documentation and the 'CNR' provider code, there are three known NS records;

https://kb.centralnicreseller.com/dns/keydns/keydns-upgrade-to-anycast

'NAMESERVER' values should be specified with a trailing dot, and, according to the documentation, there are three known NS records;

https://kb.centralnicreseller.com/dns/keydns/keydns-upgrade-to-anycast
@tlimoncelli
Copy link
Contributor

Thanks for fixing that!

@tlimoncelli tlimoncelli changed the title Update documentation to reflect current defaults CNR: Update docs with proper Nameserver example Jun 1, 2025
@tlimoncelli tlimoncelli merged commit e140acb into StackExchange:main Jun 1, 2025
2 checks passed
@mejofi mejofi deleted the patch-1 branch June 1, 2025 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants