vcsguru
asked on
Cannot Load Web Page Unless DNS is changed to Public
Hello,
Recently one of our clients vendors updated their webpage, and as a result, all clients of theirs would need to upgrade their browser to IE9 or use Google Chrome. Our client is on Server 2003, which only allows us to run up to IE8, so Chrome was our only option. What were seeing was that mostly text was resolving on the webpage, and things were not fully functional. We went though various troubleshooting steps to resolve this: reset settings to default, clear cache, flushdns, compatibility mode. All of it, no dice. So we went out on a limp and made public DNS primary and local secondary. This fixed the issue with the website, so we made the change to DHCP, and went on our way. The next day, our client reported slow log in times, and multiple SQL applications were not functioning normally. We changed the local DNS back to primary, and public back to secondary and those problems disappeared. Of course, as a result of that, the website cannot be accessed within the network. Does any one have any idea what the issue might be or how to fix it, or is our only real option to upgrade the server. Thanks!
Recently one of our clients vendors updated their webpage, and as a result, all clients of theirs would need to upgrade their browser to IE9 or use Google Chrome. Our client is on Server 2003, which only allows us to run up to IE8, so Chrome was our only option. What were seeing was that mostly text was resolving on the webpage, and things were not fully functional. We went though various troubleshooting steps to resolve this: reset settings to default, clear cache, flushdns, compatibility mode. All of it, no dice. So we went out on a limp and made public DNS primary and local secondary. This fixed the issue with the website, so we made the change to DHCP, and went on our way. The next day, our client reported slow log in times, and multiple SQL applications were not functioning normally. We changed the local DNS back to primary, and public back to secondary and those problems disappeared. Of course, as a result of that, the website cannot be accessed within the network. Does any one have any idea what the issue might be or how to fix it, or is our only real option to upgrade the server. Thanks!
With respect to DNS, you should be using internal DNS for both primary and secondary. If the primary DNS fails then the client will continue to use the secondary until secondary fails and then it will try the primary DNS again. Your configuration could lead to long logons, inability to authenticate and use internal applications.
ASKER
We have already reverted the DNS back and the logon times are fine, but any of the users behind the server are not able to properly load the site no matter which browser they are using (IE9, Chrome, Firefox) the page will only load what looks to be a Site Map and they are not able to navigate the site.
This appears to be a DNS issue as changing the DNS servers resolves the parsing errors, so is there a way to configure DNS within the domain to bypass the primary server for a specific site?
Again we are currently running server 2003 SBS, fully patched, and all WS's are Windows 7 with IE9 and generally at least one other browser.
I have attached screenshots of how the site looks from within the network and how it looks everywhere else as well for reference.
Thanks in advance.
WireBond-External.JPG
WireBond-Internal.JPG
This appears to be a DNS issue as changing the DNS servers resolves the parsing errors, so is there a way to configure DNS within the domain to bypass the primary server for a specific site?
Again we are currently running server 2003 SBS, fully patched, and all WS's are Windows 7 with IE9 and generally at least one other browser.
I have attached screenshots of how the site looks from within the network and how it looks everywhere else as well for reference.
Thanks in advance.
WireBond-External.JPG
WireBond-Internal.JPG
ASKER
@dipopo,
We are having the same issues across all browsers, it is not just limited to Chrome., but thanks for the link.
We are having the same issues across all browsers, it is not just limited to Chrome., but thanks for the link.
ASKER
I've requested that this question be deleted for the following reason:
No answers were received and we worked around with a totally different resolution
No answers were received and we worked around with a totally different resolution
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The DNS forwarder bypassed the local server which was what was causing the issues
Might be the prefetching.
http://www.mydigitallife.info/turn-off-dns-prefetching-in-google-chrome-to-fix-resolving-host-and-cannot-load-page-error/