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:
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?
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
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:
Additionally, we go into more detail about how this routing works in this support guide here:
TLDR; the domain is correctly configured and working as expected.
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.
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?
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.
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.
When querying these nameservers directly for the A record, I consistently get two IP addresses:
$ dig @dns1.p06.nsone.net jonasgloric.com A +short
18.208.88.157
98.84.224.111
Testing the Reachability of Both IPs
18.208.88.157 responds normally via HTTPS.
98.84.224.111, on the other hand, consistently fails when accessed from AT&T residential service:
Example: Using curl with debug output
$ curl -v https://98.84.224.111/
* Trying 98.84.224.111:443...
* connect to 98.84.224.111 port 443 failed: Operation timed out
* Failed to connect to 98.84.224.111 port 443: Operation timed out
* Closing connection 0
curl: (28) Failed to connect
Example: TCP traceroute fails to reach destination
This is not an AT&T issue. I can reach other sites just fine, and multiple traceroute/mtr attempts show that the route dies inside Netlify’s IP range.
Netlify support has already acknowledged 98.84.224.111 is one of their IPs, so I’m not asking for a referral to my ISP — I’m asking that this specific IP be investigated or removed from DNS rotation until it’s reachable.
Closing Thought
If one of the IPs served by your platform can’t be reached by a major ISP like AT&T, that’s a business-critical issue. I need to know that my site is reachable by all users — not just some.
Just to follow up — I’m still seeing this issue, and I’ve narrowed it down.
When I query public DNS resolvers (Cloudflare 1.1.1.1 and Google 8.8.8.8) for jonasgloric.com, both return the same two A records:
98.84.224.111
18.208.88.157
The problem: 98.84.224.111 is not reachable from AT&T (tested from multiple devices on my home connection).
Here’s what I’ve confirmed:
98.84.224.111 consistently times out — both with curl, mtr --tcp, and tcptraceroute.
18.208.88.157 works fine.
My local DNS server is bypassed in these tests — I’m querying Cloudflare and Google directly.
The bad IP is still being returned now, so it’s not a stale cache.
This implies that Netlify’s DNS is currently advertising an IP that is not reachable by a major U.S. ISP. This is likely affecting a portion of U.S. traffic. And because DNS responses rotate, it’s intermittent.
I don’t control that IP. I didn’t configure it. But my domain is answering with it — and that breaks the site for some users.
Can someone at Netlify please verify this IP allocation and remove it from rotation if it’s not viable?
hey @charles-hood thanks for getting in touch, and apologies for the issues here. Our engineering team is currently investigating similar reports of connectivity issues, and we’ll be sure to follow up here again as soon as we have more insight to share.
