Strange Client Domain Resolution Issue

[matturn]

I have a Windows 2000 client machine connected to a Windows 2003 server
via a workgroup. It's ISA server is called "isa", but it keeps
resolving the term to the IP of "isa.edu.au". I have flushed the DNS
Client Resolver Cache with ipconfig with no success. Any suggestions to
what might the problem be?

According to the user, nothing on the machine was changed around the
time of the failure except the browser's homepage...

 

[Kevin D. Goodknecht Sr. [MVP]]

I have a Windows 2000 client machine connected to a Windows 2003
server via a workgroup. It's ISA server is called "isa", but it keeps
resolving the term to the IP of "isa.edu.au". I have flushed the DNS
Client Resolver Cache with ipconfig with no success. Any suggestions
to what might the problem be?

According to the user, nothing on the machine was changed around the
time of the failure except the browser's homepage...

In your ipconfig /all I believe you will find that edu.au is in the DNS
suffix search list, which the DNS client service and Nslookup append to all
queries without a trailing "." Just to verify it run 'nslookup -d2 isa', you
will see how nslookup does its non-fully qualified name lookups. Nslookup
requires the trailing dot to consider the lookup a FQDN, then it won't
append suffixes.
How to stop this depends on whether you need a DNS suffix search list at all
since you are in a Workgroup. What you need to do is remove edu.au from the
DNS suffix search list.
If your clients are members of an AD domain it is another story. If that is
the case, there's another way to stop this that you can apply through a
group policy.

 

[Funkadyleik Spynwhanker]

I have a Windows 2000 client machine connected to a Windows 2003 server
via a workgroup. It's ISA server is called "isa", but it keeps
resolving the term to the IP of "isa.edu.au". I have flushed the DNS
Client Resolver Cache with ipconfig with no success. Any suggestions to
what might the problem be?

According to the user, nothing on the machine was changed around the
time of the failure except the browser's homepage...

Are you using a publicly routabable IP address for the hostname/NIC on the
server? (i.e. not using NAT)

If so, you are probably getting a reverse designation that comes from your
connection.