Win2k AD DNS Problem

[MysticLlama]

I'm having this quirky DNS problem, and I'm sure it's just something small I'm missing.

On my latest DFS shares I've made I've been using the fully-qualified domain name of the server rather than just the server name.

My older DFS shares look like this: \\servername\share
The ones I just made look like this: \\servername.domain\share

All of the shares work just fine on my machine, but the new ones don't work on anyone else's.

If I use there computer and ping servername, it works just fine, if I ping servername.domain it can't find it.

Doing a direct nslookup on my primary DNS server for the servername.domain comes back with the right IP, and I've verified that the client is using that DNS server.

The only thing that is a little off, is that the secondary DNS server that gets set is a linux box that doesn't auto-update, and doesn't have that name in there yet. Do clients ever completely bypass the first DNS server and only query off of the second?

I can go back to just using the servername, but that doesn't seem like the best way to do it to me.

 

[Tallgeese]

All the time...in fact, a lot of folks have posted horror stories about Win clients not actually querying the primary nameserver at all.

 

[Woodie]

Interesting. I was under the impression that DFS shares were of the form:
\\FQDNofDomain\Sharename. No servername listed.

The DFS Root has the table of real servernames and their respective sharepoints.

 

[Gantry]

A real quick way to determine if the secondary DNS is the problem - remove it temporarily from your client's DNS servers and try to mount the share using the FQDN....

Name resolution is one of the most troublesome issues with Win2k servers..