[nsd-users] NSD lost most part of zone

Peter Andreev andreev.peter at gmail.com
Thu Mar 29 13:13:36 UTC 2012


2012/3/29 W.C.A. Wijngaards <wouter at nlnetlabs.nl>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Peter,
>
> Were you out of disk-space (so, the file was truncated) ?  Did the
> computer reset during the nsd-patch zone write or something like that?
>

No for both questions.

>
> Otherwise, do you have the last changes (ixfr.db, nsd.db, ... other
> unnatural incidents) for debug analysis?
>

I made a lot of "update-rebuild-patch" trying to retransfer full zone, so
these files are changed heavily.
Another unnatural incident is that when I do "nsdc patch", NSD says
"warning: slave zone example.com with no zonefile
'/srvs/nsd/etc/slave/example.com.S'(No such file or directory) will force
zone transfer." but no file appearing, neither right after command issued,
nor after some time passed.

# ls -l /srvs/nsd/etc
total 16
drwxr-xr-x  2 apn   dns   512 Mar 27 11:59 RCS
-r--r--r--  1 apn   dns  7479 Mar 27 11:59 nsd.conf
drwxrwxr-x  2 bind  dns   512 Mar 29 14:52 slave

NSD is running under bind user.

# df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/da0p2       1G    587M    339M    63%    /
devfs          1.0k    1.0k      0B   100%    /dev
/dev/da0p4     9.9G     32M    9.0G     0%    /home
/dev/da0p5      39G    128M     36G     0%    /srvs
/dev/da0p6      39G     32M     36G     0%    /srvs/named/var/log
/dev/da0p7       4G     32M    3.6G     1%    /tmp
/dev/da0p8     9.9G     32M    9.0G     0%    /usr/BSD
/dev/da0p9     9.9G    139M    8.9G     2%    /usr/local
/dev/da0p10    7.9G     34M    7.2G     0%    /var

OS - FreeBSD 64bit.


> Best regards,
>   Wouter
>
> On 03/29/2012 01:36 PM, Peter Andreev wrote:
> > Hello list,
> >
> > I encountered weird problem with NSD 3.2.9. Suddenly it lost about
> > 90% of zone. The configuration is following:
> >
> > zone: name: "example.com <http://example.com>" zonefile:
> > "/srvs/nsd/etc/slave/example.com.S" allow-notify: master1-ip
> > xfrkey request-xfr: UDP master1-ip xfrkey
> >
> > allow-notify: master2-ip xfrkey request-xfr: UDP master2-ip xfrkey
> > allow-axfr-fallback: "yes" outgoing-interface: service-ip
> >
> > allow-notify: 127.0.0.1 NOKEY
> >
> > master1 and master2 are BIND servers, providing IXFR.
> >
> > All was good yesterday, after "nsdc patch" NSD reported about
> > ~7000000 records processed normally. Today I got: zonec: processed
> > 621379 RRs in "example.com <http://example.com>".
> >
> > Did somebody meet the same problem? Any ideas how to solve and not
> > meet this problem again?
> >
> >
> > -- AP
> >
> >
> > _______________________________________________ nsd-users mailing
> > list nsd-users at NLnetLabs.nl
> > http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQIcBAEBAgAGBQJPdFjqAAoJEJ9vHC1+BF+NRjwP/2T960JY3L6Qxqa0lfRUBNJH
> gPaa8HsViuKVAPST5OQa+rPIkSCxxqCLyUgOfm3qYdDy0zAMDRfxnDRbfJ5BuX89
> hV5nakiOwh83waO003KIJzT1fc8xi6gI3j3w5Fvw1d7hw3OrVA3AbCOpEMUblkko
> 7WYFRLv2RAtvGddEWY2TZWfaWFaSRF90LFeI+1VgbVPh/rwTHCKdGpgqtrYlRV+H
> Cn6HPgCw93Sbujg8ycWGqnNLZfIAcjbBOpdAuSuZ/ENxGsaiZwNZhSy+0UC+G9rI
> 15l9mK2zIjfxYpwi0ith1BIBfU8BzYeIYLAf2uSmrU5QSt7ROJlvuo1Mz5X4G2Xr
> qGlKfVhrVmzL2bn9JlF62I5FP7XXgfUhQYCtACyV1gc71HV7jLQ3fTYytdZa6ryn
> M0C6f1lKMic5YWWosETB8LTwiY7+pO2DHdG+QjBf0iWSHrxGlVdReLPOJ8Akr+xw
> K8UZwdvVCphmvVBtnMkqD2ViNXBia5GHm+gzJ4Jdg5uoHT2PK5+/pip3PBymC879
> MP1U3lrbsORHLXazR1evZOyiFfM67v5rAr5UZBOQRCHg9qgBKWuz6e6R0atCiL9t
> cpwXAnMDr9wmSo47ViQMe0Bbc+eOXv7yUwtJ9UMwH/uccg28C5VP37NxusWOoO2y
> wPwHu7lRcdLPBGEglGFu
> =MS7p
> -----END PGP SIGNATURE-----
> _______________________________________________
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
>



-- 
AP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20120329/3afbd3c1/attachment.htm>


More information about the nsd-users mailing list