cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Secondary DNS not being declared to the TLD.

I'm curious if this has happened to anyone else. i'm using go-daddy as the primary DNS servers for a few domains and have the service, buddyns setup as secondary. Zone fines are syncing fine, everything is working... Except if I do a DNS trace. The TLD servers only have NS records for the godaddy NS servers. This means that if go-daddy's DNS servers were unreachable, the secondary DNS wouldn't do anything to help because only go-daddy's DNS servers have records for the secondary DNS servers.

 

See example DIG output below, santitized.

 

com.                    172800  IN      NS      k.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    86400   IN      DS      30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
com.                    86400   IN      RRSIG   DS 8 1 86400 20190228050000 20190215040000 16749 . fQziINjn6jovxjKWHNQHi61xYyWUlw2f/XlcieXWZlPmnL0G0TfzXASD HxEbA1QPcZpEBhSL7Pd+NBnNQP+Ho7WDHyMSOlhdJ0DbpK8GxHILapzO HSnECcSJJJ1rySslubye3KcvIVXw1Ml5mfZPB3+iMUBfJRdlYXZZA9+X bdFqhWanGu2e5yHlU09AlsKxFTL5OojmrwohLXbUWe61GyQ0ktMIViJc 4lBFIphivOI7ovQYSRny66x05tEezn8YurftHX3V7AqWqs6J24uAk2kW MdAzR17G7bhWJw1oxe0YtUfRG6NO+8yvVcS8A+TWs1Rje0XtlQCMeOIv G32ZvA==
;; Received 1176 bytes from 202.12.27.33#53(m.root-servers.net) in 178 ms

XXXXXXXXXXX.       172800  IN      NS      pdns11.domaincontrol.com.
XXXXXXXXXXX.       172800  IN      NS      pdns12.domaincontrol.com.
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q1GIN43N1ARRC9OSM6QPQR81H5M9A NS SOA RRSIG DNSKEY NSEC3PARAM
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20190220054447 20190213043447 16883 com. k/VAeDiJifvgbRmoqyVLQesGnIP6SfqDkPqpVnej7bj4567yAE2OFxDx hBRo7VnKCndaSfxP3wPzgDk27UCNBCH6wHeFqKDCranVEJWAohh2z+Le +BytMudWZjKMlw/1tYEnD3smjX8txcuklrRH/mcVydCtzmGxnjiDMVJv yAs=
VPHIL4G3CVFTVU6V7OVSSHJ4KCR5S7UG.com. 86400 IN NSEC3 1 1 0 - VPHJ5EB40KV1DB87JL1PA09C85AI94GC NS DS RRSIG
VPHIL4G3CVFTVU6V7OVSSHJ4KCR5S7UG.com. 86400 IN RRSIG NSEC3 8 2 86400 20190222055453 20190215044453 16883 com. FBtUABIn610zzj9Z6GoxRmvALluq+kgSuvCbWVM3xeA6lnrBgFafq1MQ qcd4IVqrln9w+sWlO9DvPXmW0WBmTTWFfALItC8QcgEI3YIvzYtLa2D5 Lzo7JaIiV3f/TgBgutOa/jXO+Su2rUAChJj54LlOTTcwnvB7nMdLlyd7 NXE=
;; Received 674 bytes from 192.5.6.30#53(a.gtld-servers.net) in 30 ms

XXXXXXXXXXX.       1800    IN      A       XXXXXXXXXXX
XXXXXXXXXXX.       1800    IN      NS      d.ns.buddyns.com.
XXXXXXXXXXX.       1800    IN      NS      i.ns.buddyns.com.
XXXXXXXXXXX.       1800    IN      NS      pdns11.domaincontrol.com.
XXXXXXXXXXX.       1800    IN      NS      pdns12.domaincontrol.com.
;; Received 160 bytes from 97.74.111.55#53(pdns11.domaincontrol.com) in 15 ms

Godaddy support is telling me this how it's supposed to work.. which makes me realize that trying to talk to them is pointless.

 

This issue effects 5/10ish domains seemingly randomly. I've tried turning secondary DNS off and on, rebuilding the DNS settings, no change. Hoping someone else found a work-around?

1 REPLY 1
Community Manager
Community Manager

Re: Secondary DNS not being declared to the TLD.

Hi @mtz4718. Thanks for being part of GoDaddy Community! By design, our system shouldn't report two sets of nameservers. It checks DNS resolution for the master nameservers and if it finds that there is a problem, it starts to push out the information for the slave nameservers. Once the problem with the primary nameservers is resolved, it starts pushing that information out again. Getting results that show your secondary nameservers shouldn't happen unless there is a problem with the primary set. If you are seeing this happen 5/10 times, then I'd say something is amiss and our advanced support team should take a closer look. You may need to contact our support team again if your secondary nameservers are showing up repeatedly. 

 

JesseW - GoDaddy | Community Manager | 24/7 support available at x.co/247support | Remember to choose a solution and give kudos.