DYN DNS not updating / propagating since 5+ hours

T

TGanter

New Member
Hi,

for some hours now my dynamic IP is not propagated. I find no notice of maintenance or outages, and I find no tools to verify what the issue is.
I understand that propagation to the internet may take time, but …

… I see the *correct* IP addresses in the DNS Panels.
1736886471388.png

… I get the *wrong* IP addresses when I query designated zoneedit DNS servers.
1736886380003.png

Is there anything I am missing, or is there currently an issue?

Greetings,
—Thomas
 
… and yes, I have tried to set the IP manually to a different IP just to see whether that would propagate, but I still only get the wrong old address no matter what i try.
 
We have experienced this same issue. Have spent 2 1/2 hours troubleshooting the propogation of an updated record. I'm getting the sense that is is someone on ZoneEdit side.
 
sparkyit said:
We have experienced this same issue. Have spent 2 1/2 hours troubleshooting the propogation of an updated record. I'm getting the sense that is is someone on ZoneEdit side.
Click to expand...

THANK YOU for confirming that I am not a complete idiot.

Now I wonder why there is no status and/ or announcement from ZoneEdit side.
 
we have been working on fixing this issue.... affected zones should be working very soon now .. I am sorry for the inconvenience.
 
sandy said:
we have been working on fixing this issue.... affected zones should be working very soon now .. I am sorry for the inconvenience.
Click to expand...
Thanks for the update.
Is there any page (status.zoneedit.com) where „commonly known issues“ are posted?
(would make me feel less like an idiot)
 
TGanter said:
No, the issue seems to be fixed now.
Thanks for fixing it — but what can be done to be quicker on top of a similar situation in the future?
Click to expand...

You can check if the system is hung publishing the new zone by making a small change, such as adjusting the SOA record. Set the "expire after" from 1 week to 2 weeks (or vice versa). That will cause the zone to reload. Use an external DNS checker site (such as dnschecker.org) to verify if there was any change. If that doesn't work. Contact support.
 
Chris Cherry said:
You can check if the system is hung publishing the new zone by making a small change, such as adjusting the SOA record. Set the "expire after" from 1 week to 2 weeks (or vice versa). That will cause the zone to reload. Use an external DNS checker site (such as dnschecker.org) to verify if there was any change. If that doesn't work. Contact support.
Click to expand...

Guess what — same Issue happens right now.
And I checked the SOA, updated the expiry, and it did (again) NOT propagate.
 
TGanter said:
Guess what — same Issue happens right now.
And I checked the SOA, updated the expiry, and it did (again) NOT propagate.
Click to expand...
@Chris Cherry , @zesupport , @sandy — yesterday issue resolution was quicker.
Is there a systemic issue with my Zone file — or is there just some technical problem not fully resolved on your end?

Just asking, as there were next to no issues in the past 20 years, and now two within 12 hours …
 
Unfortunately still not working for me.

DNY muzej.stamcar.com is set to 89.212.235.46 in CP, but DNS still showing 91.246.240.39 :(

And I do thank ZoneEdit for the many years of flaweless free service! Hoping this can be resolved soon :)
 
Same problem for me - got a new IP address 10 hours ago and DYN field is updated but zone not propagated. Tried changing the SOA time back and forth and save, but no luck.
 
Hellow i have same problems on my domain, I make some change records and the result is old data and new records not propagate. SOA register not change after updates.
 
We are experiencing the same issue as we did last night again. The ticket from last night was resolved, but this seems to be a reoccuring malfunction.
 
Hang in there, guys. This is likely caused by a server update that was made yesterday. It has similar symptoms to the issue for which I provided the workaround. We have our devs/ops looking into it.
 
It should be fixed now; the affected zones are almost all reloaded. Let me know if you see otherwise.
 
You must log in or register to reply here.
Back
Top