Windows DNS Question

Hello,

I would like to know about the Windows for Domains with single label DNS names.

I have been reading about this topic today and would like to get some real world feedback regtarding this subject.

So if you have a domain name say testme.ad , then you don't have dynamic updates? I found this Microsoft KB 300684 -Information about configuring Windows for domains with single-label DNS names.

One thing that I do not understand is how can you not have A records and PTR records for these clients.

Because as of now none of our clients are adding records to our DNS, and I have the checkbox checked for register your connection in DNS.

So I do not know if I have something else going on, or is this the way it is starting with windows 2003, xp, 2000 pro sp4.

So from this kb article, I might have to configure the clients to work with DNS dynamically.

Has anyone have this situation before?

Thanks,

Mike

What version Server OS are you using? 2000 or 2003? Single lable domains are A HEADACHE! As a contracted IT provier, I have walked into new environments where there environment was setup in a single label domain and reinstalled the OS and gave their domain a proper naming convention, ususlly businessname.local.

As to why you're clients aren't updating their DNS records is because you need to configure them to use the stated single label domain name as its' DNS namespace. Within the Windows DNS structure it's essentially not seeing your DNS server as authoritative for that domain namespace (single labels reference NetBIOS names of domains. Have you ever tried to just visit Yahoo as opposed to Yahoo.com?) and it doesn't know where to register its' information. This can cause slooow login, poor network performance and the inability to properly locate network resources. (And yes, you'll need to configure EACH client via that article. So use the Grop Policy method described so you won't need to go to EACH workstation)

If you're forced to use the single label donmain, that is a very good article, follow it to a 'T' and you should be fine...

Hi, PWD

Thanks for the great comments. We are using Windows 2003 ENT and some R2.

So would you call say testmerb.ad

Because I join computers just using testmerb and not testmerb.ad

So if I'm correct you can use .local .anything and that would be consider a single label domain?

Thanks,

Mike

A single label domain name would be something like the following:

A proper local domain naming scheme would be something like the following:


Since your domain is already setup to use a single name and you're running a 2003 infrastructure, you should follow the directions in the provided link so you won't have to redo you're entire domain...You can use Group Policy to push the needed settings to your clients.

Hi, PWD

So I do not have a single label domain, according this your examples.

So are your refering to the microsoft KB that I posted eailer?

Thanks,

-Mike

If you are using testme.ad then no, you do not have a single label domain name...The NetBIOS name of your domain would be testme

Now, as to why your're clients are not updating in DNS is the true mystery. If you add clients via testme that should be just fine.

Let's Cover Some Basics
Is the DNS Server service currently running? Is your domain's forward lookup zone set to 'AD integrated' and allowing 'Secure' Dynamic Updates? Are you using DHCP? And if so, in the 'Scope Options' are they configured to use the LAN IP address of your DC as their DNS server? Is your DC currently configured to use it's own IP address as it's DNS server (in your server's connections properties)? In your Scope Options in DHCP do you have option 15 'DNS Domain Name' set to your domain of testme.ad ?