AD - DNS breakage (I think)

[Shantu Roy]

Hi all,
Hopefully someone can clue me in to something stupid that
I might be doing. Well the senario goes as such..
We have one domain controller in our domain, it is
running win2k (SBS 2000 + SP4) and dns is running on a
freebsd box with BIND. Recently when trying to add
machines to the domain I get an error about not being
able to contact the domain controller and looking furhter
it appears to be a dns problem. Essentially when I try
and add the machine using the Network ID wizard, if I try
and join the domain XYZ it fails, but when I try and join
XYZ.COM the dns srv record resolves but fails saying that
the resolved ip is not the domain controller which is not
correct since the ip is correct. Any ideas?

Thanks

Shantu

 

[Mark Mancini]

any particula reason you are using Unix instead of AD-DNS? Yes, it is
superior but if you don't want any issues, read my dns paper in the download
section of mcse2000.com

 

[GUY]

I HAVE ONE QUESTION, IS THIS THE ONLY MACHINE THAT IS
HAVING PROBLEMS CONNECTING TO THE DOMAIN?

IF YES, CHECK THE DNS SETTINGS ON THE LOCAL MACHINE
INCLUDING THE APPEND DNS SUFFIX.

IF ALL THE MACHINES HAVE PROBLEM THEN CHECK THE VERSION OF
YOUR DNS SERVER IT MUST BE 8.1.2 TO SUPPORT SRV RECORED.

GUY

 

[Gadla Gad Lev-Ari]

try to resolve the name using nslookup the kerberos srv record in the dns server
_kerberos._tcp.default-first-site-name._sites.dc._msdcs.Domain_Name
you can also try to resolve the _ldap in the same location.
Does your bind server support dynamic updates and the "_" underscore character?

Regards,
Gadla.

 

[Shantu Roy]

so I decied to try and install the AD-DNS and the dns
server won't run now.. Some complaint about either
being disabled or not having the correct interface mapped
to it. I did assign the loopback address (127.0.0.1) as
the dns entry on the NIC itself. The god of ad are
laughing at me..