Re: Master to Slave initial zone transfer question
In article mailman.2651.1397662255.20661.bind-us...@lists.isc.org, Jeronimo L. Cabral jelocab...@gmail.com wrote: Dear, I've implemented two Debian 7 servers with Bind9 as a Master - Slave schema. Everything works OK, but I have just a question: When a create a new zone in the Master and reload the bind9 daemon, this zone doesn't appear automatically in the Slaveit only appears if I restart the bind9 daemon in the Slave server. Is this behaviour correct or is there any statement to transfer a new zone from Master to Slave withouth restarting the bind9 daemon in the Slave ??? To pick up new zones added to named.conf, you just need to use: rndc reconfig You don't need to restart the daemon on either the master or slave. -- Barry Margolin Arlington, MA ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Master to Slave initial zone transfer question
On 4/16/2014 11:35 AM, Barry Margolin wrote:
In article mailman.2651.1397662255.20661.bind-us...@lists.isc.org,
Jeronimo L. Cabral jelocab...@gmail.com wrote:
Dear, I've implemented two Debian 7 servers with Bind9 as a Master - Slave
schema.
Everything works OK, but I have just a question:
When a create a new zone in the Master and reload the bind9 daemon, this
zone doesn't appear automatically in the Slaveit only appears if I
restart the bind9 daemon in the Slave server.
Is this behaviour correct or is there any statement to transfer a new zone
from Master to Slave withouth restarting the bind9 daemon in the Slave ???
To pick up new zones added to named.conf, you just need to use:
rndc reconfig
You don't need to restart the daemon on either the master or slave.
To quicken the update process can use also-notify in options
also-notify {
slave1.n.n.n;
slave2.n.n.n;
};
*also-notify*
Only meaningful if *notify* is active for this zone. The set of
machines that will receive a |DNS NOTIFY| message for this zone is
made up of all the listed name servers (other than the primary
master) for the zone plus any IP addresses specified with
*also-notify*. A port may be specified with each *also-notify*
address to send the notify messages to a port other than the default
of 53. *also-notify* is not meaningful for stub zones. The default
is the empty list.
best!
jim
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Master to Slave initial zone transfer question
Dear Jim, where do I have to execute the command rndc reconfig, in master
or slave ??
Thanks a lot to both.
On Wed, Apr 16, 2014 at 12:42 PM, Jim Glassford jmgl...@iup.edu wrote:
On 4/16/2014 11:35 AM, Barry Margolin wrote:
In article mailman.2651.1397662255.20661.bind-us...@lists.isc.org
mailman.2651.1397662255.20661.bind-us...@lists.isc.org,
Jeronimo L. Cabral jelocab...@gmail.com jelocab...@gmail.com wrote:
Dear, I've implemented two Debian 7 servers with Bind9 as a Master - Slave
schema.
Everything works OK, but I have just a question:
When a create a new zone in the Master and reload the bind9 daemon, this
zone doesn't appear automatically in the Slaveit only appears if I
restart the bind9 daemon in the Slave server.
Is this behaviour correct or is there any statement to transfer a new zone
from Master to Slave withouth restarting the bind9 daemon in the Slave ???
To pick up new zones added to named.conf, you just need to use:
rndc reconfig
You don't need to restart the daemon on either the master or slave.
To quicken the update process can use also-notify in options
also-notify {
slave1.n.n.n;
slave2.n.n.n;
};
*also-notify*
Only meaningful if *notify* is active for this zone. The set of machines
that will receive a DNS NOTIFY message for this zone is made up of all
the listed name servers (other than the primary master) for the zone plus
any IP addresses specified with *also-notify*. A port may be specified
with each *also-notify* address to send the notify messages to a port
other than the default of 53. *also-notify* is not meaningful for stub
zones. The default is the empty list.
best!
jim
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to
unsubscribe from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Master to Slave initial zone transfer question
On 4/16/14, 11:42 AM, Jim Glassford wrote:
To quicken the update process can use also-notify in options
also-notify {
slave1.n.n.n;
slave2.n.n.n;
};
There is no reason to use also-notify in this situation.
Please don't do this unless you know what you are doing and actually
NEED to do this.
It makes cleaning up a few years from now so much easier when you have a
sane configuration.
AlanC
signature.asc
Description: OpenPGP digital signature
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Master to Slave initial zone transfer question
Dear Alan, sorry but I don't understand...can yo help me on this please:
When create a new zone in Master and add the zone parameters in
named.conf.local, before the Slave get the new zone do I have to write by
hand the same zone parameters in Slave's named.conf.local and restart its
bind9 daemon ???
Thanks again.
JeLo
On Wed, Apr 16, 2014 at 2:17 PM, Alan Clegg a...@clegg.com wrote:
On 4/16/14, 11:42 AM, Jim Glassford wrote:
To quicken the update process can use also-notify in options
also-notify {
slave1.n.n.n;
slave2.n.n.n;
};
There is no reason to use also-notify in this situation.
Please don't do this unless you know what you are doing and actually
NEED to do this.
It makes cleaning up a few years from now so much easier when you have a
sane configuration.
AlanC
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to
unsubscribe from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Master to Slave initial zone transfer question
On 4/16/14, 1:27 PM, Jeronimo L. Cabral wrote:
Dear Alan, sorry but I don't understand...can yo help me on this please:
When create a new zone in Master and add the zone parameters in
named.conf.local, before the Slave get the new zone do I have to write
by hand the same zone parameters in Slave's named.conf.local and restart
its bind9 daemon ???
You create an entry similar to this in named.conf on the master:
--SNIP--
zone foo.example {
type master;
file master/foo.example;
};
--SNIP--
In master/foo.example you have something like this:
--SNIP--
@ in SOA stuff
@ in NS master.foo.example.
@ in NS slave1.foo.example.
@ in NS slave2.foo.example.
master IN A address.of.master.server
slave1 IN A address.of.slave1.server
slave2 IN A address.of.slave2.server
other zone data that you feel necessary
--SNIP--
On the slaves, you have something like this in named.conf:
--SNIP--
zone foo.example {
type slave;
masters { address.of.master.server;
address.of.slave1.server;
address.of.slave2.server;
};
file slaves/foo.example;
};
--SNIP--
Once you have that all in place (and without syntax errors, checking
with named-checkconf and named-checkzone), an 'rndc reconfig' on the
master followed by a 'rndc reconfig' on the slave(s) will have
everything working correctly.
Note that I don't have any idea what your distribution maintainers wants
to have in each of the broken out parts of named.conf, so if you put it
into named.conf.local or named.conf.blarb is between you and them.
If you need more assistance than this, I highly recommend Cricket Liu's
O'Reilly's Nutshell book and Ron Aitchison's Pro DNS and BIND book.
And you don't ever need to restart a named process.
AlanC
signature.asc
Description: OpenPGP digital signature
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Master to Slave initial zone transfer question
In article mailman.2653.1397662961.20661.bind-us...@lists.isc.org,
Jim Glassford jmgl...@iup.edu wrote:
On 4/16/2014 11:35 AM, Barry Margolin wrote:
In article mailman.2651.1397662255.20661.bind-us...@lists.isc.org,
Jeronimo L. Cabral jelocab...@gmail.com wrote:
Dear, I've implemented two Debian 7 servers with Bind9 as a Master - Slave
schema.
Everything works OK, but I have just a question:
When a create a new zone in the Master and reload the bind9 daemon, this
zone doesn't appear automatically in the Slaveit only appears if I
restart the bind9 daemon in the Slave server.
Is this behaviour correct or is there any statement to transfer a new zone
from Master to Slave withouth restarting the bind9 daemon in the Slave ???
To pick up new zones added to named.conf, you just need to use:
rndc reconfig
You don't need to restart the daemon on either the master or slave.
To quicken the update process can use also-notify in options
also-notify {
slave1.n.n.n;
slave2.n.n.n;
};
This will have no effect. A notify is only effective if the slave
already has the zone configured. The OP's issue is with adding new zones
to the slave in the first place.
--
Barry Margolin
Arlington, MA
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Master to Slave initial zone transfer question
In article mailman.2654.1397663394.20661.bind-us...@lists.isc.org, Jeronimo L. Cabral jelocab...@gmail.com wrote: Dear Jim, where do I have to execute the command rndc reconfig, in master or slave ?? Thanks a lot to both. Jim didn't post the rndc reconfig info, I did. You execute it on both, instead of restarting the daemon. First execute it on the master, then execute it on the slave. -- Barry Margolin Arlington, MA ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Master to Slave initial zone transfer question
On Wed, Apr 16, 2014 at 8:30 AM, Jeronimo L. Cabral jelocab...@gmail.comwrote: Dear, I've implemented two Debian 7 servers with Bind9 as a Master - Slave schema. Everything works OK, but I have just a question: When a create a new zone in the Master and reload the bind9 daemon, this zone doesn't appear automatically in the Slaveit only appears if I restart the bind9 daemon in the Slave server. Is this behaviour correct or is there any statement to transfer a new zone from Master to Slave withouth restarting the bind9 daemon in the Slave ??? Really thanks, JeLo Did you add the new zone to the slave's configuration (usually named.conf)? I assume so, or it would never load. But named.conf is only read when named is started or a 'reload' command is sent to it (rndc reload). Until then, hte slave has no way of knowing that the zone was added. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
