jhamel2
asked on
DNS Replication : Windows DNS (Prim) and Linux Bind (Sec)
Hi,
I have a primary DNS server running on Windows Server 2008 (Windows DNS) and i have a secondary DNS server running on BIND 9 (Debian Linux).
First of all, i set up a first zone on my secondary DNS (Bind) :
xxx.xxx.xxx.in-addr.arpa
Everything is good and replicating correctly with my primary Windows DNS.
But then, i try to set up additionnal zones with exactly the same settings and i have :
client XXX.XXX.XXX.XXX#55468: received notify for zone 'xxxxx.xxx': not authoritative
I have exactly the same settings for all my zones on my Windows DNS as well.
Why does it works for my reverse zone and not for standard forward zones?
Bonus question : In Windows DNS Parameters, do i have to check the "Bind Secondaries" option? I have red that its for older version of Bind that doesnt support "notify" or something like that... Is it ok to leave unchecked with Bind 9??
Thanks.
I have a primary DNS server running on Windows Server 2008 (Windows DNS) and i have a secondary DNS server running on BIND 9 (Debian Linux).
First of all, i set up a first zone on my secondary DNS (Bind) :
xxx.xxx.xxx.in-addr.arpa
Everything is good and replicating correctly with my primary Windows DNS.
But then, i try to set up additionnal zones with exactly the same settings and i have :
client XXX.XXX.XXX.XXX#55468: received notify for zone 'xxxxx.xxx': not authoritative
I have exactly the same settings for all my zones on my Windows DNS as well.
Why does it works for my reverse zone and not for standard forward zones?
Bonus question : In Windows DNS Parameters, do i have to check the "Bind Secondaries" option? I have red that its for older version of Bind that doesnt support "notify" or something like that... Is it ok to leave unchecked with Bind 9??
Thanks.
ASKER
Hi,
I add my zones in named.conf.local
Yes, i did add my standard forward zone in that files exactly like i did for the reverse zone.
I add my zones in named.conf.local
Yes, i did add my standard forward zone in that files exactly like i did for the reverse zone.
ASKER
Heres is my named.conf.local file :
//
// Do any local configuration here
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
zone "XXX.169.209.in-addr.arpa" {
type slave;
file "/etc/bind/zones/XXX.169.209.in-addr.arpa.db";
masters { 209.169.XXX.XXX; };
};
zone "mydomain.com" {
type slave;
file "/etc/bind/zones/mydomain.com.db";
masters { 209.169.XXX.XXX; };
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
Ok i found what i did wrong :
I commented "directory "/var/cache/bind" in named.conf.options since it was not my working directory (etc/bind)
All zones are transferring correctly now.
Thanks a lot !
Ok i found what i did wrong :
I commented "directory "/var/cache/bind" in named.conf.options since it was not my working directory (etc/bind)
All zones are transferring correctly now.
Thanks a lot !
The error says that bind received a notification of a change in xxxxx.xxx, but it is not authoritative for the zone.