name resolution of domain name

[gquitugua]

If I have a domain name (microsoft.com) and it is properly registered and resolves properly externally, why would resolution not happen internally. If I use nslookup on the domain on an internal client, it correctly points to the external ip of the organization but when I enter in the domain in IE on an internal client, it shoots me to a search engine (google). Is there something I need to do to my internal DNS server so it resolves properly? Here's the kicker. We have 2 records registered with our registrar, (microsoft.com &

http://www.microsoft.com).

Both resolve correctly outside the org. In IE, when you type in

http://www.microsoft.com,

the site comes up. When you type in

http://microsoft.com,

the site brings up the search engine. Any ideas?

 

[Serbtastic]

What happens when you use the external IP address in IE internally?

 

[smah]

This happens with some soho routers that do not do loopback properly. Advise if all the following are true:[ol][li]The webserver hosting the site in question is on the local lan, the same lan as the clients that are showing this problem.[/li][li]Port forwarding is used on the router to allow external access to the webserver[/li][li]There is no internal DNS server, the client machines are configured to use the ISP's or some external DNS server[/li][/ol]With some routers under these conditions, the web address resolves correctly to the public IP of the router (as you've said that it does), but the router doesn't know to 'loopback' to the internal server when the request actually comes from the inside.

If this fits, preferred order of possible resoution steps would be (reboot is reqired to test each possibility)[ol][li]Set the client pc's to use the router's internal IP address as their DNS server, not the ISP's DNS. The router's DNS should still be the ISP's DNS servers. Depending on the router's capabilities, you might not be able to do this and/or all names might not resolve for the client pc's. But if it works, this is the way to go.[/li][li]Leave the DNS settings alone and modify the hosts file of every client pc with the server name & internal IP address.[/li][li]Add a DNS server to the internal network.[/li][/ol]

 

[gquitugua]

FYI,

I resolved it. Just so you know this is a corporation, not SOHO. The issue is we have our internal clients shooting straight to our webservers in the DMZ. I tried to what Serbtastic suggested and timeout at the gateway (ISA) which reflected in the browser. I monitored my connections and saw the connection was getting denied. I checked the host file on the ISA box and saw there was a static route for

http://www.microsoft.com

but none for microsoft.com. I added the route and flushed DNS and ARP tables and now the site shows.

Thanks for the suggestions.