We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

DNS Replication : Windows DNS (Prim) and Linux Bind (Sec)

jhamel2
jhamel2 asked
on
Medium Priority
2,218 Views
Last Modified: 2013-12-15
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.
Comment
Watch Question

CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Did you add the forward zone to the named.conf file similar to the reverse zone?

The error says that bind received a notification of a change in xxxxx.xxx, but it is not authoritative for the zone.


Author

Commented:
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.

Author

Commented:
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; };

Open in new window

CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
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 !
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.