DNS Desync: Live DNS serving old A records not visible in UI

Support
,
1

Hello,

I’ve encountered a DNS synchronization issue with my domain deskwise.io. I have successfully configured it to use Netlify DNS, and the dashboard UI looks correct.

However, your nameservers are still serving old A records from a previous host. These old records are not visible in my DNS records panel, so I cannot delete them myself.

Here is the proof from a direct nslookup against your nameserver:

C:> nslookup deskwise.io dns1.p07.nsone.net
Server: dns1.p07.nsone.net
Name: deskwise.io
Addresses: 52.52.192.191, 13.52.188.95

My site is: stalwart-salmiakki-780187.netlify.app

Based on similar topics I’ve seen in the forums, it looks like this requires a manual reset of the DNS zone on the backend. Could a support engineer PLEASE take a look and refresh the zone for deskwise.io?

Thanks!

2

Hi there, I’ve repaired the DNS zone it’s now successfully serving the site.

3

Hey thank you my friend for the help!!

I am testing and it’s still returning the old IPs for some reason when I query the nameserver directly, weird.

nslookup deskwise.io dns1.p07.nsone.net
Server: dns1.p07.nsone.net
Name: deskwise.io
Addresses: 13.52.188.95, 52.52.192.191

The DNS zone repair doesn’t appear to have taken effect yet, I’m not an expert so any advice I’d greatly appreciate. -Richard

4

Hmm, this is still not working. Can you please have a look? I hate to bother you but I have no access to fix this myself :sad_but_relieved_face:

5

Hi! I’m seeing the site currently up-and-running at deskwise.io. Are you seeing different behavior?

Additionally, I see the expected DNS records:

% dig www.deskwise.io +short
98.84.224.111
18.208.88.157

% dig NS deskwise.io +short
dns1.p07.nsone.net.
dns4.p07.nsone.net.
dns3.p07.nsone.net.
dns2.p07.nsone.net.

% dig A deskwise.io +short
98.84.224.111
18.208.88.157
6

Hey Sid,

Thank you very much for checking the dig output and confirming the NS records. I really appreciate your time on this my friend. I did my homework to save you time…

To clarify, my website project is hosted directly on Netlify at stalwart-salmiakki-780187, and we are using Netlify DNS to route deskwise .io to it.

Regarding the A records you’re seeing for deskwise.io (98.84.224.111 and 18.208.88.157), these aren’t the expected Netlify load balancer IPs for an apex domain.

According to the docs, they recommended the A record value should be 75.2.60.5.

The current behavior suggests there might be an inherited or stuck A record within the DNS zone on your backend that’s overriding the automatic NETLIFY type records visible in my dashboard. I’ve double-checked my Netlify DNS panel, and I do not see any A records with these 98.84.224.111 or 18.208.88.157 values that I can manually delete or edit. This prevents deskwise.io from correctly routing to our deployed project on Netlify.

(further evidence…skip if this is common!)…

My nslookup directly against your nameserver (dns1.p07.nsone.net) also consistently returns these non-Netlify IPs, confirming the live DNS zone is serving them:

C:> nslookup deskwise. io dns1.p07.nsone. net
Server: dns1.p07.nsone. net
Address: 2620:4d:4000:6259:7:7:0:1

Name: deskwise.io
Addresses: 52.52.192.191, 13.52.188.95

Thank you again for your help!

7

I’m still at an impasse sadly, I’ve run out of options here. Would somebody please help me?