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.
jhamel2Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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


0
jhamel2Author 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.
0
jhamel2Author 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

0
arnoldCommented:
run rndc status, how many zones does it show that it knows about 2,3?
run also rndc reconfig and check the /var/log/messages for any entries.
Is the Bind server referenced in the zone with an NS record?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jhamel2Author 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 !
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.