Usage: nsd-control [options] command
Remote control utility for nsd server.
Version 4.0.3. Report bugs to <nsd-bugs@nlnetlabs.nl>.
Options:
-c file config file, default is /usr/local/etc/nsd/nsd.conf
-s ip[@port] server address, if omitted config is used.
-h show this usage help.
Commands:
start start server; runs nsd(8)
stop stops the server
reload [<zone>] reload modified zonefiles from disk
reconfig reload the config file
repattern the same as reconfig
log_reopen reopen logfile (for log rotate)
status display status of server
stats print statistics
stats_noreset peek at statistics
addzone <name> <pattern> add a new zone
delzone <name> remove a zone
write [<zone>] write changed zonefiles to disk
notify [<zone>] send NOTIFY messages to slave servers
transfer [<zone>] try to update slave zones to newer serial
force_transfer [<zone>] update slave zones with AXFR, no serial check
zonestatus [<zone>] print state, serial, activity
serverpid get pid of server process
verbosity <number> change logging detail
Quote from: rainer_d on June 19, 2014, 08:03:22 AM
I'm thinking of moving everything to NSD.Quote
I just *love* the fact that today we have choices. When tinydns was released, it was *the* alternative. PowerDNS came along and provided an alternative to BIND for the anti-djb crowd. It really wasn't until NSD, Knot, and Yadifa that there was a market of competitive choices. Six months ago I switched one tinydns to NSD and a few days ago I switched out BIND for Knot on another. So I'm running tinydns, NSD, and Knot.Quote from: rainer_d on June 19, 2014, 08:03:22 AM
Today, it's a horrible, unholy mess of a convoluted BIND-setup, with a 15-year legacy (yeah, we run an open resolver - on purpose).
I remember first separating auth from recursive in 2000, and it was "a little bumpy" then. It proved easiest to move auth servers to new IPs and leave the old servers as caches, because so many systems pointed at them. Having done so, you get a lot of new options you didn't have before.Quote from: rainer_d on June 19, 2014, 08:03:22 AM
Thankfully, management has finally agreed to move everything to NicTool (mostly, because nobody could come up with anything better in a short time, which is (IMO) no surprise to anyone who has been watching this place.
There are alternatives to NicTool (some are actually great), but each one comes with a different set of trade-offs and a different five- or six-figures price-tag....
I am aware of managed DNS providers who provide the equivalent of "NicTool + a cluster of DNS servers," but the cost for anything more than a handful of domains starts getting very pricey very fast. It only makes sense if you need "special" features like GeoDNS, or you don't have servers to deploy on. I have a number of clients that deployed several VPSes with NicTool because that saves them $1,000/month that it costed to use Managed DNS services.
Page created in 0.093 seconds with 10 queries.