rndc (and now nsupdate too)

Mike Hoskins (michoski) michoski at cisco.com
Fri Aug 1 13:14:06 UTC 2014

-----Original Message-----
From: Tony Finch <dot at dotat.at>
Date: Friday, August 1, 2014 at 5:31 AM
To: Reindl Harald <h.reindl at thelounge.net>
Cc: "bind-users at lists.isc.org" <bind-users at lists.isc.org>
Subject: Re: rndc (and now nsupdate too)

>Reindl Harald <h.reindl at thelounge.net> wrote:
>> Am 31.07.2014 um 21:08 schrieb /dev/rob0:
>> >
>> > The proper tool to manage zone data is nsupdate(8).  Likewise well
>> > suited for automation.
>> zone file *editing*?
>> sorry, no, i developed 2008 a interface to create all zone files based
>> on database records, write the complete zone content in a main table
>> with a textfiled and a second textfiled where translation for NAT/WAN
>> zones happens and so there is and never was a reason to *edit* a
>> zone file
>> it is created from scratch when changes in a zone happen and cronjobs
>> only pull zones with the "updated-field" set to 1
>In our setup, changes made in the database are turned into an nsupdate
>script, so we don't need to bounce the name server and we can use
>BIND's automatic signing.

no argument on nsupdate, but even if you copy files around...you don't
need to bounce the nameserver, unless rndc reload is what you mean (when i
hear bounce i think stop/start).

More information about the bind-users mailing list