Chris,
Ok there are still 3 zones that are stuck. Please check the bind logs using
some monitoring script to find zone loading errors that sometimes persist for
several days. I had to do the same in the days when I loaded the FTP zone file.
(egrep "named.* zone .*(error|failed)" $log; grep "named.* malformed"
$log)
Rob
On 2024-04-25 10:51, Chris via 44net wrote:
Mea culpa!
I noticed that the updates were running way too often, i.e. it was incrementing the
serial even when no updates had occurred, on checking the code I spotted the bug causing
this and thought i had fixed it. In fact I had introduced another bug that meant NO
updates were being run!
I have now fixed the issue, and tested to make sure!!
Apologies,
Chris - G1FEF
—
ARDC Administrator
Web:
https://www.ardc.net
On 25 Apr 2024, at 08:31, Rob PE1CHL via 44net
<44net(a)mailman.ampr.org> wrote:
The updates have been stuck since late April 23, at serial number 2024042318
We'll probably have to wait until the issue has been resolved.
Before that, they were applied on the hour.
On 2024-04-24 23:41, G4FDL via 44net wrote:
I made some DNS changes to my subdomain yesterday
and around 2 hours later they showed up in DNS when I used nslookup. I later made some
more amendments but it's now 24 hours later and they still don't show.
Are the changes transferred in batches? if so what is the update frequency?
Thanks
Max
G4FDL
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org