starred/nsedit

Fork 0

mirror of https://github.com/tuxis-ie/nsedit.git synced 2026-04-27 00:25:50 +03:00

[GH-ISSUE #42] SOA timestamp not updated or incorrectly updated #21

New issue

Closed

opened 2026-02-28 01:20:35 +03:00 by kerem · 7 comments

kerem commented

2026-02-28 01:20:35 +03:00

Owner

Originally created by @harkx on GitHub (Apr 15, 2015).
Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/42

I have many zones that don't get an updated SOA timestamp after changing records. However, some do. I compared the zones, nothing fancy. (ns records, a cname for the www and that's it) All my zones are native.

I just created a new zone and it uses 20150409xx and increments this number, with 2 numbers everytime. (but today is 20150415) Time/date on the server are correct.

Is something wrong on my end or can someone confirm seeing this also?

Originally created by @harkx on GitHub (Apr 15, 2015). Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/42 I have many zones that don't get an updated SOA timestamp after changing records. However, some do. I compared the zones, nothing fancy. (ns records, a cname for the www and that's it) All my zones are native. I just created a new zone and it uses 20150409xx and increments this number, with 2 numbers everytime. (but today is 20150415) Time/date on the server are correct. Is something wrong on my end or can someone confirm seeing this also? ![ns](https://cloud.githubusercontent.com/assets/7738282/7153603/0229117e-e34e-11e4-8727-689bee04a409.png)

kerem closed this issue

2026-02-28 01:20:35 +03:00

kerem commented

2026-02-28 01:20:36 +03:00

Author

Owner

@tuxis-ie commented on GitHub (Apr 15, 2015):

The soa is updates by the API, not by nsedit. Look in your powerdns database for domain meta settings for something called soa-edit-API, iirc..

Mark Schouten
Tuxis Internet Engineering
mark@tuxis.nl / 0318 200208

On 15 Apr 2015, at 09:01, "Kristof Hardy" notifications@github.com wrote:

I have many zones that don't get an updated SOA timestamp after changing records. However, some do. I compared the zones, nothing fancy. (ns records, a cname for the www and that's it) All my zones are native.

I just created a new zone and it uses 20150409xx and increments this number, with 2 numbers everytime. (but today is 20150415) Time/date on the server are correct.

Is something wrong on my end or can someone confirm seeing this also?

—
Reply to this email directly or view it on GitHub.

@tuxis-ie commented on GitHub (Apr 15, 2015): The soa is updates by the API, not by nsedit. Look in your powerdns database for domain meta settings for something called soa-edit-API, iirc.. ## Mark Schouten Tuxis Internet Engineering mark@tuxis.nl / 0318 200208 > On 15 Apr 2015, at 09:01, "Kristof Hardy" notifications@github.com wrote: > > I have many zones that don't get an updated SOA timestamp after changing records. However, some do. I compared the zones, nothing fancy. (ns records, a cname for the www and that's it) All my zones are native. > > I just created a new zone and it uses 20150409xx and increments this number, with 2 numbers everytime. (but today is 20150415) Time/date on the server are correct. > > Is something wrong on my end or can someone confirm seeing this also? > > — > Reply to this email directly or view it on GitHub.

kerem commented

2026-02-28 01:20:36 +03:00

Author

Owner

@harkx commented on GitHub (Apr 15, 2015):

Thanks for the quick reply and useful info. Now I know that nsedit has nothing to do with incrementing the SOA. :-)

I don't have any meta settings (but will look to be sure). I do notice there's a similar issue on the pdns github page, I will look at that and close this. (I'm using PowerDNS 3.4.3)

https://github.com/PowerDNS/pdns/issues/2377

@harkx commented on GitHub (Apr 15, 2015): Thanks for the quick reply and useful info. Now I know that nsedit has nothing to do with incrementing the SOA. :-) I don't have any meta settings (but will look to be sure). I do notice there's a similar issue on the pdns github page, I will look at that and close this. (I'm using PowerDNS 3.4.3) https://github.com/PowerDNS/pdns/issues/2377

kerem commented

2026-02-28 01:20:36 +03:00

Author

Owner

@harkx commented on GitHub (Apr 15, 2015):

But on the other hand, when I use my (ancient) poweradmin, that one does update the serial correctly. On every zone. Doing the same with nsedit (on zones that update correct in poweradmin) they don't get updated at all. :(

@harkx commented on GitHub (Apr 15, 2015): But on the other hand, when I use my (ancient) poweradmin, that one does update the serial correctly. On every zone. Doing the same with nsedit (on zones that update correct in poweradmin) they don't get updated at all. :(

kerem commented

2026-02-28 01:20:36 +03:00

Author

Owner

@tuxis-ie commented on GitHub (Apr 15, 2015):

Yes, poweradmin does change the SOA. However, pdns requests that we let pdns change the SOA if required.

nsedit sets the domainmetadata for newly added domains according to: https://doc.powerdns.com/md/authoritative/domainmetadata/

You might need to do that by hand for existing domains (soa_edit and soa_edit_api).

@tuxis-ie commented on GitHub (Apr 15, 2015): Yes, poweradmin does change the SOA. However, pdns requests that we let pdns change the SOA if required. nsedit sets the domainmetadata for newly added domains according to: https://doc.powerdns.com/md/authoritative/domainmetadata/ You might need to do that by hand for existing domains (soa_edit and soa_edit_api).

kerem commented

2026-02-28 01:20:36 +03:00

Author

Owner

@harkx commented on GitHub (Apr 15, 2015):

I added meta data for all the existing domains (like you suggested). Incrementing now works most of the time so I still suspect there's a bug in pdns somewhere.

However, when creating a new zone it always gets created with this timestamp: 2015040901

This is probably also pdns related?

@harkx commented on GitHub (Apr 15, 2015): I added meta data for all the existing domains (like you suggested). Incrementing now works most of the time so I still suspect there's a bug in pdns somewhere. However, when creating a new zone it always gets created with this timestamp: 2015040901 This is probably also pdns related?

kerem commented

2026-02-28 01:20:36 +03:00

Author

Owner

@tuxis-ie commented on GitHub (Apr 15, 2015):

Yes, nsedit does nothing with serials.

Met vriendelijke groeten,

--
Kerio Operator in de Cloud? https://www.kerioindecloud.nl/
Mark Schouten | Tuxis Internet Engineering
KvK: 61527076 | http://www.tuxis.nl/
T: 0318 200208 | info@tuxis.nl

Van: Kristof Hardy notifications@github.com
Aan: tuxis-ie/nsedit nsedit@noreply.github.com
Cc: Tuxis Internet Engineering V.O.F. mark@tuxis.nl
Verzonden: 15-4-2015 11:59
Onderwerp: Re: [nsedit] SOA timestamp not updated or incorrectly updated (#42)

I added meta data for all the existing domains (like you suggested). Incrementing now works most of the time so I still suspect there's a bug in pdns somewhere.
However, when creating a new zone it always gets created with this timestamp: 2015040901
This is probably also pdns related?
—
Reply to this email directly or view it on GitHub.

@tuxis-ie commented on GitHub (Apr 15, 2015): Yes, nsedit does nothing with serials. Met vriendelijke groeten, -- Kerio Operator in de Cloud? https://www.kerioindecloud.nl/ Mark Schouten | Tuxis Internet Engineering KvK: 61527076 | http://www.tuxis.nl/ T: 0318 200208 | info@tuxis.nl Van: Kristof Hardy notifications@github.com Aan: tuxis-ie/nsedit nsedit@noreply.github.com Cc: Tuxis Internet Engineering V.O.F. mark@tuxis.nl Verzonden: 15-4-2015 11:59 Onderwerp: Re: [nsedit] SOA timestamp not updated or incorrectly updated (#42) I added meta data for all the existing domains (like you suggested). Incrementing now works most of the time so I still suspect there's a bug in pdns somewhere. However, when creating a new zone it always gets created with this timestamp: 2015040901 This is probably also pdns related? — Reply to this email directly or view it on GitHub.

kerem commented

2026-02-28 01:20:36 +03:00

Author

Owner

@harkx commented on GitHub (Apr 15, 2015):

Thanks! I'll look it up on pdns, sorry for the trouble :)

@harkx commented on GitHub (Apr 15, 2015): Thanks! I'll look it up on pdns, sorry for the trouble :)

kerem referenced this issue

2026-02-28 01:21:10 +03:00

[PR #21] [MERGED] [FIX] short_open_tag can be off now, replaced <? with <?php #138