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

[richrz]

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!

[sid.m]

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

[richrz]

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

[richrz]

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

[sid.m]

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

[richrz]

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!

[richrz]

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

[sid.m]

@richrz

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

If configuring external DNS, this is the IP address you would see configured. However, since you’ve configured Netlify DNS, the requests will be routed to the nearest CDN node to the user making the request. This means the IP address will vary depending on location. You can see those varying addresses by location looking up the domain here:

DNS Propagation Checker - Global DNS Checker Tool

Additionally, we go into more detail about how this routing works in this support guide here:

[Support Guide] How are requests routed to the nearest Netlify CDN node?

Last reviewed by Netlify Support in December 2024 This happens automatically, assuming that you’ve followed the DNS configuration best practices. When your DNS is setup reasonably, our CDN is designed to intelligently route your visitors to the CDN node nearest them on the network. This means that European visitors will load their site from a node in Europe, Australians from Australia, etc. The net result is less latency for your visitors when browsing your site. But that’s not what you aske…

TLDR; the domain is correctly configured and working as expected.

[richrz]

Not sure why but a forum rule is blocking me from replying documenting my situation, weird! Try #2!

Hi again,

Thanks for the page, I read it carefully. I understand that the traffic will eventually hit different CDN nodes closer to the user.

However, my concern is not about the dynamic CDN IPs, but about the static A record that Netlify’s own nameservers (dns1.p07.nsone.net) are publishing for the apex domain deskwise .io .

My nslookup query directly to your nameserver (dns1.p07.nsone. net) continues to show the old, incorrect IP addresses, not a Netlify load balancer IP (like 75.2.60. 5). Those 13.52.188. 95 and 52.52.192.19 1 IPs are not Netlify IPs.

Here is the current output confirming this:

nsloo kup deskwise.io dns1.p07.nsone. net

Server: dns1.p07.nsone. net
Address: 2620:4d:4000:6259:7:7:0 :1

Name: deskwis e. io
Addresses: 13.52.188. 95 and 52.52.192.191

Since my Netlify DNS dashboard correctly shows Netlify records for deskwise.io (implying it should point to my deployed project stalwart-salmiakki-780187 .netlify. app), but your own nameservers are still serving these old, external A records, it means the site is still not resolving to my Netlify project.

Could you please investigate why your nameservers are still serving these incorrect A records for deskwise.io and ensure the proper Netlify A record (75.2.60. 5) is published, or that the Netlify record is correctly overriding any lingering stale A records on the backend?

Thank you for your continued care!

[richrz]

I’m still experiencing this issue. Can anyone please help?

[sid.m]

Hi again,

I’ll try to rephrase what I stated earlier.

When using Netlify DNS, we do not expect that the A record for the domain will resolve to 75.2.60. 5. The IP addresses you’re seeing are Netlify IP addresses. We are correctly serving the site, there is no misconfiguration here.

You can verify with a curl request as well:

% curl -I https://www.deskwise.io
HTTP/2 200 
age: 264304
cache-control: public,max-age=0,must-revalidate
cache-status: "Netlify Durable"; hit; ttl=31271695
cache-status: "Next.js"; hit
cache-status: "Netlify Edge"; fwd=miss
content-type: text/html; charset=utf-8
date: Tue, 15 Jul 2025 22:53:16 GMT
etag: "1gqg9fvwprc9b"
netlify-vary: query=__nextDataReq|_rsc,header=x-nextjs-data|x-next-debug-logging|next-router-prefetch|next-router-segment-prefetch|next-router-state-tree|next-url|rsc|accept-encoding,cookie=__prerender_bypass|__next_preview_data
server: Netlify
strict-transport-security: max-age=31536000
vary: RSC,Next-Router-State-Tree,Next-Router-Prefetch,Next-Router-Segment-Prefetch,Accept-Encoding
x-content-type-options: nosniff
x-nextjs-date: Sun, 13 Jul 2025 04:48:20 GMT
x-nextjs-prerender: 1
x-nextjs-stale-time: 300
x-nf-request-id: 01K084NN48H2JDS4VB7EJRRTYG
x-powered-by: Next.js
content-length: 15893

[charles-hood]

I’m having a very similar problem. Sometimes you ping my custom domain (which I registered new on Netlify, I might add), and you get an address that actually resolves to my website (18.208.88.157), other times, you get 98.84.224.111 which resolves to nothing and eventually times out. VERY FRUSTRATING. I wish someone would take this problem seriously.

[sid.m]

@charles-hood Could you specify the domain?