DNS Resolving Fails with Windows XP

  • Thread starter Thread starter Ben M. Schorr - MVP
  • Start date Start date
B

Ben M. Schorr - MVP

Aloha Lukas,

Have you tried flushing the DNS cache to see if that resolves it? The easiest
way is to right-click on the wireless connection (either on the tray icon
or in Network Connections) and choose "Repair." Among other things that
will flush the DNS cache.

-Ben-
Ben M. Schorr, MVP
Roland Schorr & Tower
http://www.rolandschorr.com
Microsoft OneNote FAQ: http://www.factplace.com/onenote.html
 
Dear all,

at my company, I got a brand-new laptop with Windows XP SP2 installed
and configured. It is used there with wired connections and makes
use of the ISP's DNS server. This works, I can connect to my private
server at home <http://www.lpr.ch> and work as expected.

At home, I make use of a wireless connection. In my intranet, I
have my own DNS server that provides -- for obvious reasons -- some
addresses differently than to the outside.

DNS resolving to the same symolic name, i.e. <http://www.lpr.ch>
*fails* with Windows XP. For strange reasons, always the exterior
address as used from the company site is provided to any application.
I tried to re-configure the wireless lan connection by providing
the fixed IP address of my intranet DNS-Server -- without success.
To me it seems as if Windows XP SP2 would cache the DNS resolving
*stupidly*.

With *Linux*, the DNS resolving *works* as a expected like a charm.
Hence, it must be Windows specific. I assume it must be a caching
problem since the company's ISP doesn't provide DNS service to the
world.

Therefore my question:
- does anybody know of this problem?
- how can it be solved provided I already defined a fixed IP address
for the DNS server for the wireless connection.
- the DNS cache -- or whatever it is -- must be correctly
flushed/resetted everytime any network interface is (re-)configured.

Thanks in advance for any hint!

Best regards,
Lukas
 
Hi Ben,
Ben M Schorr - MVP [Thu, 11 May 2006 17:52:49 +0000 (UTC)]:

Have you tried flushing the DNS cache to see if that resolves it? The easiest
way is to right-click on the wireless connection (either on the tray icon
or in Network Connections) and choose "Repair." Among other things that
will flush the DNS cache.
Click to expand...

unfortunately: no effect -- the old address is still in the "cache".

Any other idea?

Thanks for your help!

Lukas
 
Aloha Lukas,

Odd. You don't have it in a HOSTS file on the workstation do you?

-Ben-
Ben M. Schorr, MVP
Roland Schorr & Tower
http://www.rolandschorr.com
Microsoft OneNote FAQ: http://www.factplace.com/onenote.html
Hi Ben,
Ben M Schorr - MVP [Thu, 11 May 2006 17:52:49 +0000 (UTC)]:

Have you tried flushing the DNS cache to see if that resolves it?
The easiest
way is to right-click on the wireless connection (either on the tray
icon
or in Network Connections) and choose "Repair." Among other things
that
will flush the DNS cache.
Click to expand...
unfortunately: no effect -- the old address is still in the "cache".

Any other idea?

Thanks for your help!

Lukas
Click to expand...
 
Dear Ben,
Ben M Schorr - MVP [Thu, 11 May 2006 23:50:06 +0000 (UTC)]:
Ben M Schorr - MVP [Thu, 11 May 2006 17:52:49 +0000 (UTC)]:

Have you tried flushing the DNS cache to see if that resolves it?
The easiest way is to right-click on the wireless connection
(either on the tray icon or in Network Connections) and choose
"Repair." Among other things that will flush the DNS cache.
Click to expand...
unfortunately: no effect -- the old address is still in the
"cache".
Click to expand...
Odd. You don't have it in a HOSTS file on the workstation do you?
Click to expand...


no, I've never changed anything in a file. The only thing I have
done after it failed: I added the IP Address of my intranet DNS
directly into the network settings of the wireless connection --
since I use wireless at home only.

Any idea further?

Thanks for your help!

Lukas
 
Back
Top