21 reputation
2
bio website
location
age
visits member for 6 months
seen Oct 17 '13 at 22:00

Oct
17
comment DNS resolution fails in web browser but nslookup succeeds
Thanks, Santi and Dave. We do not have DirectAccess enabled. We do have VPN enabled, but that is run through a different machine than the DNS server, and the affected client machines are not connected to VPN when the problem occurs. VPN does not seem to be involved in the equation at all.
Oct
11
comment DNS resolution fails in web browser but nslookup succeeds
The DNS servers are assigned by DHCP. When the computer is on the company network, it uses our internal DNS server. When the user is at another location it uses the DNS server specified by that location. The issue persists even if a public DNS server is manually specified (such as Google's Public DNS at 8.8.8.8 or 8.8.4.4).
Oct
10
comment DNS resolution fails in web browser but nslookup succeeds
Cold boot, yes. I have not tried a local account yet, but I will tomorrow. Any other ideas?
Oct
2
comment DNS resolution fails in web browser but nslookup succeeds
The output from a comprehensive nslookup command from an affected client (Scenario 2) is at the pastebin link below (too long for an in-comment paste). http://pastebin.com/w0DS8LyP
Oct
2
comment DNS resolution fails in web browser but nslookup succeeds
Thanks, Edwin and Craig. I just tried disabling NetBIOS and WINS is not set; this did not resolve the problem. I have also tried setting WINS on the client machines and passing WINS through the firewall to no avail. These issues prevail on any type of connection -- the consistent theme is that it only affects company-owned computers using the standard company software image. NLA is not an issue -- the issues persist regarding of the location type (Work/Home/Public). The issue persists across all browsers, testing is primarily conducted on Google Chrome. No proxies are configured.
Sep
27
comment DNS resolution fails in web browser but nslookup succeeds
Thanks for the suggestion! Yes, as described in Scenario 2, requests that use the IP address instead of the FQDN are successful. Also, as described by Scenario 4, users that are not using company-issued computers have no trouble accessing this server using the FQDN from off-site locations.
Sep
27
comment DNS resolution fails in web browser but nslookup succeeds
Thanks for the question! Unfortunately, no, all attempts to access the server using company.com or any subdomain.company.com fail -- there are about 10 different CNAME and A records that point to that server and all fail in Scenario 2. Accordingly, both company.com and www.company.com fail in that scenario.
Sep
27
awarded  Editor
Sep
27
revised DNS resolution fails in web browser but nslookup succeeds
Added edits to indicate that nslookup has been run in all four scenarios
Sep
27
comment DNS resolution fails in web browser but nslookup succeeds
Thanks for the suggestion. DNS is provided by the DHCP server, not group policy, so when a user leaves our physical building they receive the DNS server of whatever network they connect to. I have run nslookup in all cases, and it returns the correct DNS settings in all cases (including the failure case in Scenario 2). The problem seems to be that for some reason the web browsers are not even bothering to go as far as nslookup -- as described above, they simply fail without initiating any network transaction in Scenario 2.
Sep
27
comment DNS resolution fails in web browser but nslookup succeeds
Yep, I agree. Budgets are tight, what can I say. Maybe in the future...
Sep
27
awarded  Student
Sep
27
asked DNS resolution fails in web browser but nslookup succeeds