NXDomain for Netlify DNS entries?

Support
1

Hey, all!

TL;DR: Using Netlify DNS, but my DNS entries do not seem to exist or show up at all.

I’ve got my domain (lyte.dev) pointed to Netlify’s Nameservers as best as I can tell:

$ nslookup -type=NS lyte.dev
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
lyte.dev        nameserver = dns1.p02.nsone.net.
lyte.dev        nameserver = dns2.p02.nsone.net.
lyte.dev        nameserver = dns4.p02.nsone.net.
lyte.dev        nameserver = dns3.p02.nsone.net.

Authoritative answers can be found from:

Pick a random nameserver to query:

$ nslookup dns1.p02.nsone.net
...
Address: 198.51.44.2

And it has my main site’s entries:

$ dog lyte.dev A @198.51.44.2
A lyte.dev. 20s   100.28.201.155
A lyte.dev. 20s   34.234.106.80

But no entries for some of my other subdomains:

$ dog files.lyte.dev A @198.51.44.2
Status: NXDomain
SOA lyte.dev. 1h00m00s A "dns1.p02.nsone.net." "domains+netlify.netlify.com." 1664495885 12h00m00s 2h00m00s 14d0h00m00s 1h00m00s

And obviously the big DNS providers do not have the entries either:

$ dog files.lyte.dev A @8.8.8.8
Status: NXDomain
SOA lyte.dev. 30m00s A "dns1.p02.nsone.net." "domains+netlify.netlify.com." 1664495885 12h00m00s 2h00m00s 14d0h00m00s 1h00m00s

So my servers are completely unreachable. And I’m trying to understand why that would be. This seems to have started in the last few days, presumably after my router got a new address from my ISP and a script I use to update my DNS entries via Netlify’s API (homebrew dynamic DNS I suppose) attempted to update this and something has gone sideways.

I saw another support thread related to this about the NETLIFY DNS entry types. I have not needed these historically for subdomains. Has this changes recently or something?

Thanks for your help!

2

Hi, @lytedev. Would you please test deleting the non-working DNS record and then creating it again? If that does not resolve the issue, please let us know.

4

I’ll give it a shot and report back. Thank you!

5

That seems to have worked, but not a step that I would expect to be necessary. Is this a bug on your end or am I supposed to delete entries before updating them as a part of using your DNS API?

6

Hey there, sometimes our DNS records can not sync properly with our NS1 DNS provider. The easiest way to force a resync is to delete and re-add. This happens infrequently so you shouldn’t expect to have it happen again.

Thanks!