Hello friends...
I don't know if this behavior is a bug or not, but the fact is: when I use Zentyal as DNS Server for a Windows 2003 Server (standard sp2) and when I try to deploy a Active Directory, I receive, from Windows logs, the warning that could not update dns...
So, what I do is go to linux console and changing the following line in two files of bind9 configuration:
First file: named.conf.local
zone "home.lan." IN {
type master;
file "/var/lib/bind/db.home.lan";
// update-policy {
// The only allowed dynamic updates are A records
// grant home.lan. subdomain home.lan. A TXT;
// Grant from localhost
// grant local-ddns zonesub any;
// };
};
zone "200.168.192.in-addr.arpa" {
type master;
file "/var/lib/bind/db.200.168.192";
// update-policy {
// The only allowed dynamic updates are PTR records
// grant home.lan. subdomain 200.168.192.in-addr.arpa. PTR TXT;
// Grant from localhost
// grant local-ddns zonesub any;
// };
};
zone "1.168.192.in-addr.arpa" {
type master;
file "/var/lib/bind/db.1.168.192";
// update-policy {
// The only allowed dynamic updates are PTR records
// grant home.lan. subdomain 1.168.192.in-addr.arpa. PTR TXT;
// Grant from localhost
// grant local-ddns zonesub any;
// };
};
I put a "//" on lines that grant update from home.lan and subdomain... Here, I see that bind also set a zone to my external network like 192.168.1.X... That useless... But the way, this is what I do....
And the second file: named.conf.options
I need to put allow-update { any; } ; This line do not exist in such file...
All I do in those file, is necessary in order to allow Windows 2003 update de DNS Zone...
So, after make those changes, I was able to correctly configure Active Directory, having Zentyal as a DNS to Windows 2003...
My question is: is there a bug in Bind,Zentyal or Windows 2003???
Thanks... And sorry if I mess all that I wrote... rs... My English is awful.