FQDN vs Downlevel Domain Name Problem

[Matthew Kaess]

Here's what I have. We are running a custom web app that
needs to resolve the SRV record for the ldap server. Our
problem is that when our AD was set up, the Domain Name
was created differently from the original NT domain name.
Normally MYDOMAIN becomes mydomain.com when you run
dcpromo. In our case our NT domain was upgraded to W2K
and the DNS name was changed from mydomain.com to
newdomain.com leaving the downlevel name MYDOMAIN. The
problem arises when the app attempts to resolve
_ldap._tcp.Default-First-Name-Site.dc._msdcs.MYDOMAIN -
it doesn't resolve. To troubleshoot this - I added the
forward zone MYDOMAIN with the correct child domain
entries and the issues went away, but this is rediculous.
Shouldn't this still work even though there is some
ambiguity in domain naming?

 

[Deji Akomolafe]

The problem is not that you changed it to newdomain.com. It is that your
"downlevel" domain name is MYDOMAIN. It's a single-labeled domain name that
(beginning from SP4) causes some belly-aches for AD. Search for
"single-label" on this newsgroup and you'll come up with some good materials
from Keving and Ace

http://support.microsoft.com/default.aspx?kbid=300684

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon

 

[Matthew Kaess]

I'm not sure I was clear on my original post. When you
run dcpromo on an upgraded NT4.0 PDC - the wizard
automatically takes the NT domain name MYDOMAIN and
appends the .com. You can change the FQDN at that point
and that's what we did. We changed mydomain.com to
newdomain.com -BUT- left the NT name of ABC_DOMAIN as the
pre-windows 2000 downlevel name. I have a FQDN in DNS. Am
I making any sense with this?