In article ,
Jim Pazarena wrote:
> I had TWO named.conf files for my slaves, one not being used
> any longer, and THAT'S the one I updated with these new entries.
I can't count the number of times this has happened to someone.
Checking for this has long been one of my standard troubleshooting
Jan-Piet Mens wrote, On 2011-11-23 12:21 AM:
I have 1 domain name, and 1 reverse in-addr.arpa
citires.ca and0-127.254.194.207.in-addr.arpa
which my two slaves log that the master is "not authoritative" for
I found the issue!
I had TWO named.conf files for my slaves, one not
Jan-Piet Mens wrote, On 2011-11-23 12:21 AM:
I have 1 domain name
citires.ca
which my two slaves log that the master is "not authoritative" for
Seen from here (.DE) the NS for citires.ca both refuse to answer
queries, so they are indeed not authoritative:
$ dig @ns.qcislands.net
> I have 1 domain name, and 1 reverse in-addr.arpa
> citires.ca and0-127.254.194.207.in-addr.arpa
>
> which my two slaves log that the master is "not authoritative" for
Seen from here (.DE) the NS for citires.ca both refuse to answer
queries, so they are indeed not authoritative:
I have 1 domain name, and 1 reverse in-addr.arpa
citires.ca and0-127.254.194.207.in-addr.arpa
which my two slaves log that the master is "not authoritative" for
I have plenty of rdns subnets, and 3 fractional subnets in that group
so my copy & paste of this new /25 looks 100%. y
5 matches
Mail list logo