6 Feb
2012
6 Feb
'12
1:25 p.m.
Hi Max,
On Mon, February 6, 2012 9:12 am, Max B wrote:
The way I look at
it, any issues that force me to deal this change are directly relevant to
'renumbering for clients'.
The problem is that you could be running all manner of services and so any
guidance could never hope to be exhaustive. I think all we can expect is
notification from our provider that the numbering is to change.
Advice/guidance on how to accomodate that change at the network level
(i.e. adapter settings) are obviously beneficial but we can't expect the
provider to extend that advice to any and all service that we might also
be running.
'rndc reload' is a misnomer; traditionally,
under system V unix naming
conventions, 'bind' would restarted by an /etc/init.d script, either
'bind' or a catchall like 'networking'. 'rndc reload' is odd
enough to
deserve a comment on 'renumbering for clients'.
A restart of BIND via the init.d script would've also worked. The use of
rndc however is just more-targetted lowlevel management tool; there's
nothing odd about it to someone familiar with configuring/controlling
BIND. A wiki page on IP renumbering is not the place to educate the
management of BIND as there are far better resources out there already for
that.
Mathew