Ensure that the allow-query clause on the master includes the slave. If the
slave can't query for the SOA on the zone it can't do an xfer.
On Mar 2, 2017 6:34 AM, "Xavier Humbert"
wrote:
> The whole configuration, comments removed :
>
> -- Master --
> acl my-slaves {
Is this the zone in question?
master:
zone "in.acv.orion.education.fr" {
wrong on slave:
zone "in.acv.orion.education.gouv.fr" {
Regards, Edda
Am 02.03.17 um 12:33 schrieb Xavier Humbert:
The whole configuration, comments removed :
-- Master --
acl my-slaves {
The whole configuration, comments removed :
-- Master --
acl my-slaves {
any;// DEBUG
};
acl my-clients {
any;// DEBUG
};
options {
// IP config
listen-on port 53 {172.29.16.135; 127.0.0.1; };
listen-on-v6 port 53 {none; };
//
Xavier Humbert wrote:
>
> I'm really lost. I've configured dozens of DNSs with no such problems.
> Did I miss something obvious ?
I can't see anything obvious... Did you obfuscate the zone name so we
can't see if there's a typo?
Tony.
--
f.anthony.n.finchhttp://dotat.at/ - I xn--zr8h puny
Hello, I cannot fix a master/slave problem on RHEL7 with bind 9.9.4. It
is a server in building process, in a LAN, so I cannot use tools like
Zonecheck. Please note that my boss explicitely asked me to anonymize
the zone name. I know this is useless.
I can provide named.conf files for both servers
5 matches
Mail list logo