• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DNS Failing on WiFi

t3h l337 n3wb

Platinum Member
Hey all,

I've got a peculiar situation. Connected to the WiFi at my girlfriend's place right now but there are intermittent problems with resolving hostnames. She can get on the Internet just fine, but I get a DNS lookup failed. This happens on and off. I can still login to Skype and some other IM clients though.

I've tried Google DNS and OpenDNS, but both yield the same result. I can ping both of these DNS servers, but nslookup times out:

nslookup google.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 208.67.222.222

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.

nslookup 8.8.8.8
Server: resolver1.opendns.com
Address: 208.67.222.222

DNS request timed out.
timeout was 2 seconds.

These are the other things I've tried so far:

- ipconfig /flushdns
- ipconfig /registerdns
- netsh winsock reset
- startting/stopping the DNS service

I also have a Verizon LTE aircard, which is working just fine. Any ideas?
 
try to run an nmap -vv against both 8.8.8.8 and 4.2.2.2 and see if they've got port 53 open . . .
you could also simply 'telnet 8.8.8.8 53' i think is the syntax
maybe your provider is blocking DNS requests to servers other than their own? comcast? comcasts is 75.75.75.75 (and .76)
 
Back
Top