I recently change the ip address of our website, and made the changes to our in house DNS. The users that use this DNS cant get to the new site but outside of the company the site open up fine. if i perform a NSLOOKUP on one of the pc's it resolves fine. If i ping the address i get replies. i just can't open the site interally on using Internet Explorer. I have a seperate pc, that i used a public DNS and it works fine. The zone was already created, but i had to create a reverse lookup. completely confused.

I would bet your outside DNS is using cached information. Also, you should check in the IIS settins, general properties if I recall, and make sure the website is set to respond on that IP, or all IP's. My Knee jerk reaction.BlankMonkey

If they are using cached information how do i get around that? Regarding the IIs, I'm not running it on this DNS machine, do i need to be? appreciate the help!Brent Gordon

also, strangely enough, when i do a tracert, the first 10 attempts time out, and then the 11th connects. No jumps in between. Brent Gordon

Hi Traceroute is very often blocked by routers (blocking ICMP) which causes a timeout. This is not a problem. The last hop will be the web server which apparently isn't blocking ICMP. You said that the address is resolving correctly using nslookup both inside and outside, right? Are you sure both are returning the new address? It is possible that outside is still pointing to the old address, which is why it's working. -Greg P.S. Did you submit a change request to the DNS servers that are used by the domain registrar?

the way it is set up here is that our domain registar is network solution, and points to ATT as DNS manager. There is where i edited my A records. I know that the nslookup is resolving correctly because if i use the dns that was provided by my internet provider, instead of my internal dns, the site opens. if i use mine it does not. Brent Gordon

Hi, Do you use a proxy server for web access from inside the corporate network? Can you provide the name of the domain? Are your internal computers pointing to a caching/resolving DNS server or to an authoritative DNS server? Does your internal authoritative server use conditional forwarding of DNS requests for this domain to the ISP's DNS server? -Greg

sorry for the delay, was out of the office No i do not use a proxy server the domain name is petroleumwholesale.com not sure how to tell whether it is a Caching/resolving DNS or authoritive There was and i change the ip address to the location of my new web page. 174.120.62.92 Brent Gordon

Hi Brent, I know that the nslookup is resolving correctly because if i use the dns that was provided by my internet provider, instead of my internal dns, the site opens. if i use mine it does not. Logon your internal dns server, run command "dnscmd /clearcache" and "ipconfig /flushdns" to clear DNS server/client cache. Then run nslookup to verify if resolve the URL correctly. If the resolving still failed, please post nslookup and dns server ipconfig /all results to us for analysis. RegardsRick Tan TechNet Community Support

Hi Brent, Is the name of your internal domain the same as the website? You said that you made changes to in-house DNS when you changed the web server address, so it looks like you do have the domain hosted internally but this isn't necessary if the only purpose of the domain is for the website. Assuming internal DNS servers are able to resolve Internet names, you can just delete the domain from your internal DNS servers and this will allow them to search on the Internet for the correct IP address. Currently, your domain is hosted by att.net DNS servers (cbru.br.ns.els-gms.att.net and cmtu.mt.ns.els-gms.att.net). These are the servers that hold the "authoritative" data. The data that is important here are the records for www.petroleumwholesale.com and petroleumwholesale.com (with no "www"). I noticed that when you try to open www.petroleumwholesale.com that the web server redirects you to petroleumwholesale.com. This could be the problem if you forgot to change both records internally. You might have only changed the www record. Bottom line is that if you don't need to host the domain internally because it is only used for the web site, just delete it from your internal DNS servers. If you do need it interally because you use it in Active Directory, then please check that both the www.petroleumwholesale.com and the petroleumwholesale.com records were changed to 174.120.62.92. FYI, when you configure a DNS zone on a server this tells the server that it is authoritative and doesn't need to look anywhere else for information about that domain. When this is done on an internal and an external server it can cause records to get out of sync, so it generally isn't recommended to use the same name for a domain internally and externally. -Greg