I recently migrated a domain I own from Cloudflare to Netlify DNS, so I had to update my nameservers. When I run a recursive DNS lookup that bypasses DNS cache everything seems to be set up correctly:
$ dig howtogit.net +trace (output truncated) howtogit.net. 20 IN A 220.127.116.11 ;; Received 57 bytes from 18.104.22.168#53(dns1.p01.nsone.net) in 18 ms
However, a regular DNS lookup fails:
$ nslookup howtogit.net Server: 192.168.1.1 Address: 192.168.1.1#53 ** server can't find howtogit.net: SERVFAIL
I assume that if caching was at fault, Cloudflare would still resolve the lookup which it doesn't. A lookup at 22.214.171.124 (Google's DNS) also fails:
$ dig @126.96.36.199 howtogit.net ; <<>> DiG 9.10.6 <<>> @188.8.131.52 howtogit.net ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 63809 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;howtogit.net. IN A ;; Query time: 43 msec ;; SERVER: 184.108.40.206#53(220.127.116.11) ;; WHEN: Sun Sep 23 13:05:50 CEST 2018 ;; MSG SIZE rcvd: 41
Since DNS records are cached, I also tried flushing Google's DNS cache for my NS and A records. I'm still getting the same result, despite the change having happened over 10 hours ago.
Is my configuration incorrect? How do I make sure my DNS can resolve properly again?