rndc (and now nsupdate too)

[Reindl Harald]

Am 01.08.2014 um 15:44 schrieb Mike Hoskins (michoski):
>>> 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)
>>
>> since when is -SIGHUP stop/start?
> 
> i suspect a language barrier, since if you read what i typed i never said
> that.  in fact, i'm not sure you read what Tony typed either.
> 
> "bouncing a daemon" often means stop/start.  whether you rndc reload or
> HUP, such a restart is not needed on zone changes.  my entire point is
> that a costly full restart is not needed, even without nsupdate.
> 
> i'm sure Tony knows this, and simply wanted to clarify for posterity in
> the thread archive.

no it is *not* a language barrier
you are simply missing the context

the whole discussion about rndc or not rndc follow up
therads and side-threads startet after that reply below
from me yesterday and whoever brought "bounce" in the
game did also not understand the context of the discussion

all the threads about "rndc" refer to that below!

-------- Weitergeleitete Nachricht --------
Betreff: Re: rndc (and now nsupdate too)
Datum: Thu, 31 Jul 2014 14:08:48 -0500
Von: /dev/rob0 <rob0 at gmx.co.uk>
Antwort an: bind-users at lists.isc.org
Organisation: RTFM
An: bind-users at lists.isc.org

On Thu, Jul 31, 2014 at 05:56:08PM +0200, Reindl Harald wrote:
> Am 31.07.2014 um 17:41 schrieb /dev/rob0:
> > On Thu, Jul 31, 2014 at 01:32:03PM +0200, Reindl Harald wrote:
> >> i am doing reloads of named with "killall -HUP named" just
> >> because i disabled rndc completly for security reasons and
> >> configurations are generated with own software only needs
> >> named to reload

-------- Weitergeleitete Nachricht --------
Betreff: Re: Reload BIND to listen on additional interface?
Datum: Thu, 31 Jul 2014 13:32:03 +0200
Von: Reindl Harald <h.reindl at thelounge.net>
An: bind-users at lists.isc.org

Am 31.07.2014 um 13:24 schrieb Johannes Kastl:
> in the quest to use a master behind a Router with changing IPs, I set
> up a VPN and told bind on both sides to listen on the additional VPN-IPs.
>
> But, sometimes they are not available at bind startup or the VPN loses
> connection. So, when the VPN connection is ready again, I can let
> OpenVPN run a script. My idea was to use this script to tell bind,
> that it can now bind to the interface again.
>
> Question now is, which (rndc) command does that? Does a ‘rndc
> reconfig‘ tell BIND to newly bind to the interfaces?

i am doing reloads of named with "killall -HUP named" just because i
disabled rndc completly for security reasons and configurations
are generated with own software only needs named to reload

pretty sure it will also force look for new interfaces or gone ones

[root at srv-rhsoft:~]$ tail named.log
#31-Jul-2014 13:30:05.016 general: automatic empty zone: D.F.IP6.ARPA
31-Jul-2014 13:30:05.016 general: automatic empty zone: 8.E.F.IP6.ARPA
31-Jul-2014 13:30:05.016 general: automatic empty zone: 9.E.F.IP6.ARPA
31-Jul-2014 13:30:05.016 general: automatic empty zone: A.E.F.IP6.ARPA
31-Jul-2014 13:30:05.016 general: automatic empty zone: B.E.F.IP6.ARPA
31-Jul-2014 13:30:05.016 general: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
31-Jul-2014 13:30:05.037 general: reloading configuration succeeded
31-Jul-2014 13:30:05.039 general: reloading zones succeeded
31-Jul-2014 13:30:05.057 general: all zones loaded
31-Jul-2014 13:30:05.057 general: running

[root at srv-rhsoft:~]$ killall -HUP named

[root at srv-rhsoft:~]$ tail named.log
31-Jul-2014 13:30:26.443 general: automatic empty zone: D.F.IP6.ARPA
31-Jul-2014 13:30:26.443 general: automatic empty zone: 8.E.F.IP6.ARPA
31-Jul-2014 13:30:26.443 general: automatic empty zone: 9.E.F.IP6.ARPA
31-Jul-2014 13:30:26.443 general: automatic empty zone: A.E.F.IP6.ARPA
31-Jul-2014 13:30:26.443 general: automatic empty zone: B.E.F.IP6.ARPA
31-Jul-2014 13:30:26.443 general: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
31-Jul-2014 13:30:26.446 general: reloading configuration succeeded
31-Jul-2014 13:30:26.447 general: reloading zones succeeded
31-Jul-2014 13:30:26.464 general: all zones loaded
31-Jul-2014 13:30:26.464 general: running

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20140801/4c4ff499/attachment.bin>