Utican
asked on
DNS Issues w/ IE10; FireFox 37 Working (OpenDNS)
Hello,
I'm experimenting with using OpenDNS. I've stumbled across an issue when using IE 10 where websites are unreachable. Here's a breakdown of what's happening:
1) Via IE and FF, all internal and external websites are reachable with existing DNS with DHCP IP and DNS
2) Manually pointed DNS to OpenDNS servers and receiving DHCP IP
3) Using IE, external sites resolve without an issue; some internal sites receive an unreachable
3a) For the unreachable sites, able to resolve the proper IP address and ping the host; nslookup verifies it's information
3b) Placed the IP within the URL and it cannot retrieve the site
4) When using FF, I am able to resolve the internal sites I could not reach as described within 3a & 3b
5) I revert my DNS settings to receive original DNS information via DHCP, and IE will work
This is perplexing as this definitely sounds like an IE issue, since FF is working without a hitch. The problem is that the user base is predominantly IE and as we roll the out in the future, they will begin to experience the same issue.
Thanks
I'm experimenting with using OpenDNS. I've stumbled across an issue when using IE 10 where websites are unreachable. Here's a breakdown of what's happening:
1) Via IE and FF, all internal and external websites are reachable with existing DNS with DHCP IP and DNS
2) Manually pointed DNS to OpenDNS servers and receiving DHCP IP
3) Using IE, external sites resolve without an issue; some internal sites receive an unreachable
3a) For the unreachable sites, able to resolve the proper IP address and ping the host; nslookup verifies it's information
3b) Placed the IP within the URL and it cannot retrieve the site
4) When using FF, I am able to resolve the internal sites I could not reach as described within 3a & 3b
5) I revert my DNS settings to receive original DNS information via DHCP, and IE will work
This is perplexing as this definitely sounds like an IE issue, since FF is working without a hitch. The problem is that the user base is predominantly IE and as we roll the out in the future, they will begin to experience the same issue.
Thanks
ASKER
Thanks, to be more granular, we have the OpenDNS appliances installed and its forwarding internal requests to our internal servers. All externals are then forwarded to the OpenDNS recursive on the Internet.
Is there a way to clear the FF cache? I flushed DNS and it didn't work. Maybe OpenDNS thinks the internal request is external, so it's not forwarding it properly to the internal DNS, rather OpenDNS?
Is there a way to clear the FF cache? I flushed DNS and it didn't work. Maybe OpenDNS thinks the internal request is external, so it's not forwarding it properly to the internal DNS, rather OpenDNS?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When one has access to internal LAN DNS, there is absolutely no reason/benefit to altering that other than bypassing what site restriction there might be.
You've identified the cause and the remedy, when 1-4 apply 5.
You've identified the cause and the remedy, when 1-4 apply 5.
You should continue to use your internal as a primary and set your DNS servers to query the appliance for external domains
ASKER
Thanks for getting my brain thinking :)
What you should do is have your gateway/router forward external DNS requests to OpenDNS instead of hard-coding it into the network settings on the machine.