[GH-ISSUE #165] notify pdns after zone update #107

Closed
opened 2026-02-28 01:21:01 +03:00 by kerem · 3 comments
Owner

Originally created by @Rico29 on GitHub (Feb 2, 2018).
Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/165

Possibility to enable notification via API when a change is made on a zone

Originally created by @Rico29 on GitHub (Feb 2, 2018). Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/165 Possibility to enable notification via API when a change is made on a zone
kerem closed this issue 2026-02-28 01:21:02 +03:00
Author
Owner

@tuxis-ie commented on GitHub (Feb 2, 2018):

Please explain?

<!-- gh-comment-id:362590159 --> @tuxis-ie commented on GitHub (Feb 2, 2018): Please explain?
Author
Owner

@Rico29 commented on GitHub (Feb 2, 2018):

Hello, tuxis-ie
Sorry, I want to create a pull request with changes I made...

I added a flag "notifyafterupdate" in config.inc.php. when this flag is set to true, then a notify is sent to slaves via the API :
https://docs.powerdns.com/authoritative/http-api/zone.html#put--servers-server_id-zones-zone_id-notify

Just need to pull-request it

<!-- gh-comment-id:362591315 --> @Rico29 commented on GitHub (Feb 2, 2018): Hello, tuxis-ie Sorry, I want to create a pull request with changes I made... I added a flag "notifyafterupdate" in config.inc.php. when this flag is set to true, then a notify is sent to slaves via the API : https://docs.powerdns.com/authoritative/http-api/zone.html#put--servers-server_id-zones-zone_id-notify Just need to pull-request it
Author
Owner

@HLFH commented on GitHub (Mar 17, 2018):

It seems I had the issue one year ago with my slave that did not get the notify after DNS updates via nsedit.

It has changed now. The feature "Send a DNS NOTIFY to all slaves" is happening without https://github.com/tuxis-ie/nsedit/pull/166 commits.

My master and my slave are correctly configured. And I'm already receiving correctly the notify. @tuxis-ie Can you close the PR https://github.com/tuxis-ie/nsedit/pull/166 and this issue? This code will bloat nsedit and it should be done at the configuration level in pdns.conf with only-notify=::/0 to force IPv6 master/slave communication, and in the pdns database with supermasters table well set-up.

<!-- gh-comment-id:373941135 --> @HLFH commented on GitHub (Mar 17, 2018): It seems I had the issue one year ago with my slave that did not get the `notify` after DNS updates via nsedit. It has changed now. The feature "Send a DNS NOTIFY to all slaves" is happening without https://github.com/tuxis-ie/nsedit/pull/166 commits. My master and my slave are correctly configured. And I'm already receiving correctly the `notify`. @tuxis-ie Can you close the PR https://github.com/tuxis-ie/nsedit/pull/166 and this issue? This code will bloat `nsedit` and it should be done at the configuration level in `pdns.conf` with `only-notify=::/0` to force IPv6 master/slave communication, and in the `pdns` database with `supermasters` table well set-up.
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/nsedit#107
No description provided.