'succesful' nsupdate of remote server not persistent across nameserver restart?

Alan Clegg alan at clegg.com
Mon May 2 14:21:58 UTC 2016

On 5/2/16, 10:17 AM, "Matthew Pounsett" <bind-users-bounces at lists.isc.org on
behalf of matt at conundrum.com> wrote:
> On 2 May 2016 at 10:05,  <jasonsu at mail-central.com> wrote:
>> General question --
>> When I want to change a zone file's data manually, say to add an A record,
>> what's the right procedure:
> If the zone is set up for dynamic updates, like the examples you've given,
> then in order to touch the zone file directly you need to temporarily tell
> BIND to stop managing the file.
> The general procedure is
> 1) use 'rndc freeze <zone>' to stop dynamic updates to the zone
> 2) edit the file
> 3) use 'rndc thaw <zone>' to re-enable dynamic updates
> If the zone is not set up to use dynamic updates, then:
> 1) edit the zone file
> 2) 'rndc reload <zone>'

How about just "use nsupdate" since that's what this entire discussion was
about?  Once you move to dynamic zones, doing "freeze/thaw" is silly and
disruptive of the update mechanism.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20160502/fbbfd051/attachment-0001.html>

More information about the bind-users mailing list