Local website unavailable

  • Thread starter Thread starter Scott
  • Start date Start date
S

Scott

Greetings -

My issue is with my Win2K/SP4 and WinXP/SP1a workstations not able to get to
my internal website which I have setup in my DNS as a www host to a NATed IP
address on my firewall. The strange thing is that it works sometimes and
sometimes it doesn't. My internal website will timeout for no particular
reason. Yet when I go to the workstation and at a DOS prompt use "ipconfig
/renew" - the internal website comes back. Even stranger is when the
workstations lose the ability to browse the internal website, they can still
browse external websites.

Obviously I am doing something wrong here. Can anyone shed some light on my
DNS issue? If you need more info, please let me know.

Thanks.
Scott
 
Yet when I go to the workstation and at a DOS prompt use "ipconfig
/renew" - the internal website comes back. Even stranger is when the
workstations lose the ability to browse the internal website, they can still
browse external websites.
Click to expand...

This is a classical set of symptoms seen when machines are set
with both internal and public DNS servers in their Tcp/Ip config.
If you want to use private DNS zones, then machines must only
use a path of resolution that will always that them to a DNS service
that is aware of those private zones.
 
For the internal web site, why did you give www host IP as
the NATed (public) IP address? This will be problematic.
Give the www. host IP as the private IP of the server.

Sharad
 
I have tried both scenarios <public & private IP addresses> and I am still
having the same issues.
 
So the DNS set for use in the Tcp/Ip config is your
DNS server ? Having resolution of internal names
go south, but then come back after a ipconfig /renew
often happens after the client has moved to use of the
next listed DNS server and it is incapable of resolving
the internal names, but then the renew sets the stack
back to using the initial DNS of the list.
 
Back
Top