Skip to content

CNR: Update docs with proper Nameserver example#3592

Merged
tlimoncelli merged 1 commit intoStackExchange:mainfrom
mejofi:patch-1
Jun 1, 2025
Merged

CNR: Update docs with proper Nameserver example#3592
tlimoncelli merged 1 commit intoStackExchange:mainfrom
mejofi:patch-1

Conversation

@mejofi
Copy link
Copy Markdown
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
Copy Markdown
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
AsifNawaz-cnic pushed a commit to centralnicgroup-opensource/rtldev-middleware-dnscontrol that referenced this pull request Jan 19, 2026
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