Problem with BIND DNS and AD

[Jaysheel Mehd]

TZ wrote:

>I have set up a BIND 9.2.3 DDNS on a solaris 8 platform.
>We have a W2k3 AD server that can register it self with BIND server
>with no issues. However we build a W2k server as a test to see it it
>can add it self to the domain. It registers itself to the AD server,
>but does not register in DDNS - we point it to the BIND DNS server as
>its primary DNS - am I doing it wrong?
>When rebooting the W2K server - I see the following warning in the
>event viewer but when I try a ipconfig /registerdns - nothing happens.
>
>The system failed to register network adapter with settings:
>
>   Adapter Name : {5280D8CF-8974-4229-BE55-79D381DA494B}
>   Host Name : chgdcinet3
>   Adapter-specific Domain Suffix : diamondcluster.net
>   DNS server list :
>     10.1.1.30
>   Sent update to server : None
>   IP Address(es) :
>     172.20.2.90
>
> The cause of this DNS registration failure was because of DNS server
>failure. This may be due to a zone transfer that has locked the DNS
>server for the applicable zone that your computer needs to register
>itself with.
>
> 
>Any one have any ideas?
>Thanks
>
>Tariq Zawahir
>Unix Admin
>tariq.zawahir at diamondcluster.com
>
>  
>
Check the permissions and acls (in allow-update/allo-transfer statement) 
for the related zones in named.conf. You should have an entry to allow 
your new W2K server to do DNS update or the zone transfer.

Thanks
Jaysheel