[GH-ISSUE #577] authoritative nameservers not updating from internal master #387

Closed
opened 2026-02-26 10:31:12 +03:00 by kerem · 3 comments
Owner

Originally created by @ThomasWaldmann on GitHub (Jun 17, 2025).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/577

when an IP is updated, the https://www.nsupdate.info service sends a dns update to an internal dns server - this is working correctly.

but, since about 2025-06-17 (or 16?), the internal dns server is not updating the public, authoritative dns servers (ns1.thinkmo.de and ns2.thinkmo.de) and they still serve outdated IP addresses, if the IP address changed.

we are working on finding / fixing the issue, sorry for the inconvenience!

Originally created by @ThomasWaldmann on GitHub (Jun 17, 2025). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/577 when an IP is updated, the https://www.nsupdate.info service sends a dns update to an internal dns server - this is working correctly. but, since about 2025-06-17 (or 16?), the internal dns server is not updating the public, authoritative dns servers (ns1.thinkmo.de and ns2.thinkmo.de) and they still serve outdated IP addresses, if the IP address changed. we are working on finding / fixing the issue, sorry for the inconvenience!
kerem 2026-02-26 10:31:12 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@ThomasWaldmann commented on GitHub (Jun 17, 2025):

  • v6 connectivity between internal dns server and authoritative servers is working (ping6)
  • accessing the internal dns from ns1.thinkmo.de also works (dig @...)
<!-- gh-comment-id:2979474597 --> @ThomasWaldmann commented on GitHub (Jun 17, 2025): - v6 connectivity between internal dns server and authoritative servers is working (ping6) - accessing the internal dns from ns1.thinkmo.de also works (dig @...)
Author
Owner

@ThomasWaldmann commented on GitHub (Jun 17, 2025):

an issue with the replication slots in the database was fixed and the dns servers are updating correctly now.

keeping this issue open for a while so it can be found more easily.

<!-- gh-comment-id:2979608585 --> @ThomasWaldmann commented on GitHub (Jun 17, 2025): an issue with the replication slots in the database was fixed and the dns servers are updating correctly now. keeping this issue open for a while so it can be found more easily.
Author
Owner

@hede5562 commented on GitHub (Jun 17, 2025):

Thank you for the quick solution to the problem - I can affirm it is working for me now.

<!-- gh-comment-id:2980060760 --> @hede5562 commented on GitHub (Jun 17, 2025): Thank you for the quick solution to the problem - I can affirm it is working for me now.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nsupdate.info-nsupdate-info#387
No description provided.