cannot access web page hosted by the web host

Hi all,

I used to have my web page host by a web hosting company. Since I have installed AD, DNS on my new w2k server, XP pros machine cannot access the web page. I found the DNS is pointing to the w2k server, which is used for the authenicating purpose for all XP machines. However, if I change the DNS to my ISP DNS server address, I can access it but all the XP machines will be very slow when they authicate with the w2k server.

Anyone out there has any ideas how to resolve this? Thanks

 

I moved the thread - twice. I had problems figuring out just which section it really belonged in. May still not have it right.

My guess at this point is a problem with the way you set up your internal DNS for the 2K AD. I think if you set your internal DNS server up as a root server you would see this sort of behavior. Do you know if that is how you configured things?

 

I've come across this a few times where you use the same domain name internally as that used by your external webpage.

For example, let's say I have a domain mycompany.com, and use that on my 2000 network. Also I have an external website at www.mycompany.com.

From inside you want to connect to www.mycompany.com so you request the associated IP address from the DNS server on your Win2000 server. It doesn't have a mapping for this address, but because it is its domain, it assumes that there can't be an address held anywhere and therefore doesn't look elsewhere.

The easiest solution should be to add a mapping in your DNS server for a node called "www" with the external IP address of your site. This used to work a treat on NT4, but I've been told it doesn't work for 2000.

This maybe one of the many reasons why it can be better to use a ".local" domain internally. If you're using NAT and 192.168.x.x, or 10.x.x.x address why not use a different DNS naming scheme internally too!

However, if your registered domain and therefore external website uses mycompany.com, I wouldn't recommend using mycompany.local internally as I've seen examples of win2000 reading domain names from left to right instead of right to left and this can result in confusion. I'd use a variation: something like companymy.local internally.

 

I can safely say:

I hate DNS

More like it's my total stupidity at trying to use it, but still...

Had the same problem in the past, can't stand slow client logons and policies/software installations not taking affect because of DNS problems.