Nsupdate usage scenario
prk at iment.com
Wed May 4 19:17:38 UTC 2016
Interesting idea -- it never occurred to me that I could have separate
zone files for sub-domains.
So, if I had a tiny zone file for "dynamic.example.com" alone, and a
bigger zone file for all the other stuff for "example.com", could I be
*sure* that nsupdate would *only* modify the tiny file, and not mess
with the bigger, main file?
Or would I also have to put a ZONE statement as the first line of the
nsupdate data stream specifying "dynamic.example.com" as the zone to be
updated? (And would that *guarantee* the main file was not changed?)
On Mon, 2 May 2016 14:15:21 -0500 (CDT)
"Jeremy C. Reed" <jreed at isc.org> wrote:
> What about using a specific zone file just for the purpose of the
> single A record you want to maintain using dynamic updates?
More information about the bind-users