DNS/IP problem

[Dave Peno]

I have a strange problem. Our corporate web page is hosted
off site by a hosting company. We have intermitant
problems viewing our web page. We have a WIN2000 server
with exchange, DNS, WINS, and active directory on it. The
forwarders on the DNS setup are set to our ISPs DNS
servers. The Individual PCs (WIN2000) are setup to point
to our DNS server and our ISPs DNS server as a secondary
DNS. The problem is sometimes a web browser can not see
our web page but the same pc can ping the web page using
the hostname as well as the ip address. When I talk to our
hosting company they said I should put their DNS servers
as a secondary DNS entry, but that should not be the case.
Also, when we can not see our web page we can see it on a
dial up pc that uses AOL. I have no idea what is going on.
I am not sure if this is a ip problem, DNS problem or an
overloaded DNS, WINS, Domain controller, Exchange server
issue. And yes, All of those are running on one server (
not my idea ). Anyway, any advice would be appreciated.

Dave

 

[Michael Johnston [MSFT]]

First, the clients should only point at the internal DNS server for name resolution. Do not point the clients to the ISP for DNS.

As for the problem with connectivity to the website, first make sure that the clients can resolve the name of the site. Make sure it
resolves to the correct IP address. Once name resolution has been verified, try to telnet to the website on port 80. Does this
connect? Lastly, I'd recommend taking a network trace of the problem. This can often identify exactly where the failure is
occuring.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

 

[Marina Roos]

Is your AD domainname the same as your websitename? You'll need to add a
hostrecord in DNS-server that is pointing to the public IP of your website.
And DNS on your servernic(s) should *only* point to your server-IP. DNS on
the clients should *only* point to your server-IP.