[nsd-users] Suggestions for NSD

Teran McKinney sega01 at gmail.com
Mon Sep 8 22:39:31 UTC 2008


I have been using NSD for about a month and a half and have been quite
pleased with it. From my use, I have found a couple things I would
like to suggest. I run three NSD instances, all coexisting with
Unbound for recursive resolving on seperate servers. I noticed two
awkward situations that can arise when running multiple DNS servers on
the same server. One is that `nsdc patch`, only tells localhost to
patch. In my cases, the caching resolver would listen on ::1
(especially in the case of VPS), and NSD would sit on my IPv4 address
and an external IPv6 address. When `nsdc notify` is called, it sends a
request to ::1, which isn't too useful as the recursive resolver
catches it instead. Perhaps nsdc could read nsd.conf, and/or have an
option to send the request to a different IP? Can notifications be
done with `drill`?

The other suggestion I have for NSD is an outgoing-interfaces option,
like in Unbound. If you add aditional IP addresses to the server, you
cannot configure which IP requests go out of for AXFR requests. The
slave servers would probably be configured to only allow notifications
for zone transfer requests from the master server's address, but as
soon as the master server adds another address and it becomes a
prefered route, the notifications are denied as they go out of the
foriegn IP.

NSD is an awesome authoritive server, thank you all for the time and
effort spent on it. I hope that these suggestions are useful. Of
course, these can be worked around, but I think that a couple extra
features in this regard could make things easier and more ideal.

Let me know if anything needs to be clarified or if you have any questions.

Teran (sega01)

More information about the nsd-users mailing list