Windows 7 DNS Issue - A doozie

[JustinWPB]

I'm having a problem where dns doesn't seem to be working. But Nslookup does. Can reach web websites by their IP but not their hostname. I think I'm dealing with a corrupt driver somewhere but I've got no clue how to determine which one.

C:\Users\Sharon>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Sharon-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E Gigabit Ether
net Controller #2
Physical Address. . . . . . . . . : 00-11-D8-26-84-33
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::454f:6a28:7d17:a8b4%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.200.120(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.200.250
DHCPv6 IAID . . . . . . . . . . . : 301994456
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-A2-54-F0-00-11-D8-26-87-B8

DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
NetBIOS over Tcpip. . . . . . . . : Enabled

I had to set the IP/DNS/Gateway manually. DHCP won't work. Says something about a file of a loopback adapter not being found. I'll try to add that later.

C:\Users\Sharon>ping google.com
Ping request could not find host google.com. Please check the name and try again
.

C:\Users\Sharon>nslookup google.com
Server: resolver1.opendns.com
Address: 208.67.222.222

Non-authoritative answer:
Name: google.com
Addresses: 2607:f8b0:4002:c01::64
74.125.137.102
74.125.137.101
74.125.137.139
74.125.137.138
74.125.137.113
74.125.137.100

C:\Users\Sharon>ping 74.125.137.102

Pinging 74.125.137.102 with 32 bytes of data:
Reply from 74.125.137.102: bytes=32 time=35ms TTL=46
Reply from 74.125.137.102: bytes=32 time=30ms TTL=46
Reply from 74.125.137.102: bytes=32 time=31ms TTL=46
Reply from 74.125.137.102: bytes=32 time=35ms TTL=46

Ping statistics for 74.125.137.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 35ms, Average = 32ms

Chrome gives this error when navigating to google.com:

The webpage at http://www.google.com/ might be temporarily down or it may have moved permanently to a new web address.
Error 137 (net::ERR_NAME_RESOLUTION_FAILED): Unknown error.

However it's browse-able through 74.125.137.102. It seems like a simple dns problem except that nslookup google.com works. I've searched and searched.

One more curveball: I added

74.125.137.102 google.com

into the hosts file. Still unable to pull google.com up in chrome.

Tried all the tricks I could find. I reset the dns client via command line and gui. Reset the TCP stack. Not sure where to go next. Thanks for any help guys!

Justin

 

[JustinWPB]

Network Adapters (including hidden):

ASUS 802.11b/g Wireless LAN Card
Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller
Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller #2
Microsoft ISATAP Adapter
Microsoft ISATAP Adapter #2
Microsoft ISATAP Adapter #3
WAN Miniport (IKEv2)
WAN Miniport (IP)
WAN Miniport (IPv6)
WAN Miniport (L2TP)
WAN Miniport (Network Monitor)
WAN Miniport (PPPOE)
WAN Miniport (PPTP)
WAN Miniport (SSTP)


Clients/Protocols in use:

Client for Microsoft Windows
QoS Packet Scheduler
File and Printer Sharing for Microsoft Networks
Reliable Multicast Protocol
Link-Layer Topology Discovery Responder
Link-Layer Topology Discovery Mapper I/O Driver
Internet Protocol Version 6 (TCP/IPv6) - disabled
Internet Protocol Version 4 (TCP/IPv4)

 

[jamesmcuk]

1. try disable IPv6
2. 192.168.200.250 is an unusual address for router - is this defo correct?
3. Uninstall all Marvel Yukon from device manager and reboot allowing PC to reinstall driver and then ensure DHCP is enabled and router is setup to supply DHCP.
4. Ensure router is setup to DHCP its own DNS server addresses and they have not been manually set..
5. Try hard inputting OpenDNS server addressees into the DNS Server options on the network card.

 

[JustinWPB]

1. try disable IPv6

It's disabled.

2. 192.168.200.250 is an unusual address for router - is this defo correct?

yea, custom settings.

3. Uninstall all Marvel Yukon from device manager and reboot allowing PC to reinstall driver and then ensure DHCP is enabled and router is setup to supply DHCP.

I'll give this a shot.

4. Ensure router is setup to DHCP its own DNS server addresses and they have not been manually set..

They're manually set to OpenDNS servers. I try to stay away from anything Comcast.

5. Try hard inputting OpenDNS server addressees into the DNS Server options on the network card.

The computer's already using them. And they're working as far as nslookup is concerned. Seems like a problem with the DNS Client?

 

[Hawkeye22]

Are you sure of your DNS entries? It seems like some sites are being randomly pulled from cache and not from a lookup. If you open a command prompt and type

ipconfig /flushdns

does "nslookup google.com" still work? If not, your DNS addresses may be incorrect.