[nsd-users] zonestatus question
Klaus Darilion
klaus.mailinglists at pernau.at
Thu Jul 10 15:01:17 UTC 2014
Hi!
I had to restart nsd4. The local available zone file was rather old.
nsd[11004]: /var/lib/nsd/nsd.db: not cleanly closed 0
nsd[11004]: can not use /var/lib/nsd/nsd.db, will create anew
So, nsd started to create a new db file.
Meanwhile I checked the zonestatus:
state: refreshing
served-serial: "2014063012 since 2014-07-10T14:52:55"
commit-serial: "2014063012 since 2014-07-10T14:52:55"
notified-serial: "2014071016 since 2014-07-10T14:52:56"
transfer: "TCP connected to 83.136.34.4"
After finishing the transfer, the status was:
state: ok
served-serial: "2014063012 since 2014-07-10T14:52:55"
commit-serial: "2014071016 since 2014-07-10T14:53:13"
But if I query the SOA nsd responds with serial: 2014063012
Why does nsd still answers with the old zone?
Then I called "nsd-control write" (which gives no errors) but nsd does
not write a new zone file. And the status is:
state: ok
served-serial: "2014063012 since 2014-07-10T14:52:55"
commit-serial: "2014071016 since 2014-07-10T14:53:13"
Any hints what is wrong here?
Thanks
Klaus
More information about the nsd-users
mailing list