IE11 DNS issue

nutcase · 29 Mar 2015 at 11:15

Got an issue that I think is DNS that shows sometimes and is mildly annoying.

Environment is Server 2012 R2 with either RDP or 8.1 clients.

I've got two repeatable issues, there are other intermittent ones.

Repeatable 1: When I go to Manage Add-ons/Tracking Protection/Get a Tracking protection list online without fail I get a This page can't be displayed error. Same with find search providers.

Repeatable 2: If I type in the address https://www.halifax-online.com/ in the address bar I get the same error. If I type google in the address bar, google comes up. Searching for Halifax-online and clicking on the link works fine. Search from the address bar is enabled.

Any ideas?

Thanks

nutcase · 31 Mar 2015 at 13:54

Changing to Google does work - so I guess that just confirms it's a DNS issue?

I already have Google in the forwarders list on the DNS server, and most sites work, so not sure where to go from here?

thanks

nutcase · 2 Apr 2015 at 07:35

Tried that, and also scavenging stale records etc. on the server

It doesn't work on any of the machines connected to the domain

nutcase · 3 Apr 2015 at 06:58

If it was the ISP wouldn't it still not work when I bypassed the DNS servers?

I've not tried removing a machine from the domain - what would I look for when I did as even if it's not a member, it would still pick up the same DNS servers?

I did find something yesterday, I had to restart the secondary DNS server, and during that time DNS wasn't available at all - so it looks like the primary is doing naff all...

nutcase · 11 Apr 2015 at 11:55

Still struggling with this

BPA shows no errors for DNS. There's quite a few forwarders on the list - I've been gradually adding them over time to see if the problem goes away!

Originally it was just the google ones, but have added the plusnet, dyndns and a few others with no luck

I have found something though - some machines it works on, some it doesn't.

Those that it doesn't work on, when I run nslookup gives the UnKnown error.

That confuses me though as the "fix" is to re-do the A and PTR records - but as it works on some machines that means they're ok?