DIDWW seems to be midway between moving from GoDaddy DNS to their own
internal DNS.
Their DNS Servers are cached for 1 hour.
We started seeing DNS failures for api.didww.com which returns no entries
from
;; AUTHORITY SECTION:
didww.com. 3600 IN NS ns14.domaincontrol.com.
didww.com. 3600 IN NS ns13.domaincontrol.com.
However, when querying the root .com DNS servers, their NS records changed
web1 : /usr/local/apps --> dig didww.com @a.gtld-servers.net
;; AUTHORITY SECTION:
didww.com. 172800 IN NS ns1.didww.com.
didww.com. 172800 IN NS ns2.didww.com.
We have hardcoded the IP for api.didww.com and web-fe-api.didww.com to
continue API operations with DIDWW until the DNS caches expire and the new
information is updated.
Please, y'all -- when doing a DNS migration, ensure 1000% that your DNS
records on your old DNS provider match your DNS records on your new DNS
provider, and plan your DNS migration early by setting the TTL for your NS
records at least to 5 minutes (300 seconds) if allowed, 30 seconds if you
can.
Assume all caching servers will cache for 5 minutes even if you set it to
30 seconds.
At least that way if things go wrong, your outage horizon is 5 minutes, not
1 hour or more!!!
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beck...@angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
