DNS not resolving

[jfhoffman3]

I have a windows xp pro machine. Whether I automatically obtain a dns or statically assign it i'm not able to resolve addresses. I have other machines on the network that I have tried and they work fine. This issues is with both the lan and network card.

 

[itsp1965]

There could be a lot of issue and more information maybe required. Have you;

- actually pinged the DNS servers that have been added to your machine to ensure connectivity

- do you have a personal firewall that is blocking port 53 (DNS queries).... most probable?

- are you on a different VLAN from where the other machines are connected

 

[jfhoffman3]

-I am able to ping the IP of the DNS server.

-I do not have a personal firewall. I use windows firewall which I have disabled to troubleshoot. I use avast for my antivirus

-I am not using a VLAN. This issues is at my home and at work. I get the same results at both locations.

If i put in

http://wwww.google.com....Page

can not be displayed. If i put in 66.102.1.147...google comes up. Its not resolving any names

 

[itsp1965]

What happens when you actually try to perform an nslookup against 1. local addresses and 2. internet addresses

 

[jfhoffman3]

Both resolve

 

[itsp1965]

I am not following.. you performed an nslookup and both are able to resolve? This would indicate that the name resolution is working.

 

[jfhoffman3]

Sorry I thought I resolved...It says: Non-authoritative answer. Which I'm assuming didn't resolve.

Ping Results:

C:\>ping 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:

Reply from 4.2.2.2: bytes=32 time=27ms TTL=244
Reply from 4.2.2.2: bytes=32 time=24ms TTL=244
Reply from 4.2.2.2: bytes=32 time=23ms TTL=244
Reply from 4.2.2.2: bytes=32 time=22ms TTL=244

Ping statistics for 4.2.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 27ms, Average = 24ms

C:\>ping

http://www.google.com

Ping request could not find host

http://www.google.com.

Please check the name and try a
gain.

NSLOOKUP Results:

C:\Documents and Settings\JOHN HOFFMAN>nslookup
Default Server: carlisle00.cte.carlisle.com
Address: 192.168.1.2

> google.com
Server: carlisle00.cte.carlisle.com
Address: 192.168.1.2

Non-authoritative answer:
Name: google.com
Addresses: 74.125.127.100, 74.125.67.100, 74.125.45.100

> hacc.edu
Server: carlisle00.cte.carlisle.com
Address: 192.168.1.2

Non-authoritative answer:
Name: hacc.edu
Address: 199.254.212.100

 

[itsp1965]

It's resolving but the message indicates that your DNS servers are not authoritative for these domains and is relying on another server to manage your query.
I would compare your DNS settings again with a machine that is working. Make sure you don't have any hard coded DNS settings that are conflicting

 

[jfhoffman3]

I will look at it tonight but please understand that this issue happens on all networks. This machine for some reason will not resolve addresses to the web. Again this happens on all networks with all different dns settings. If I use it at home, buddies house, free wifi spot, or at work....same result...It is able to ping the IP but will not resolve a name. Of course each location has its own dns server.

 

[itsp1965]

Is it only web access that is the issue? Have you tried accessing an Internet service that is non-HTTP ex) FTP for instance. From what I see you either have one of the following;

- Hard coded DNS entry (ex - hardcoded DNS Suffix)
- You have a local hosts file that is pointing popular sites back to your local loopback address
- A Proxy setting in your browser which does not allow you to go out (have you tried another browser)

Otherwise this is not a DNS issue as you can both ping the DNS server and perform lookups from the command line

 

[stfaprc]

from the last jhoffman3 post on June 16th,
it sounds like the pc has a DNS record hand entered into the network configuration. I notice that the ping was made against 4.2.2.2 - is that the DNS address entered in? I thought that att (or whoever owns it) stopped allowing DNS request from unapproved addresses.

 

[Noway2]

Yes, the thread goes back a couple of days, and I assume that means that a solution has been found. If not, here are some more thoughts.

Try to temporarily set your resolver to point to a different (known DNS) and see if that works. If it does, it confirms that the problem is with your DNS.

Have you tried to ping one of these addresses after you have done an nslookup on it? By doing the nslookup, it should be in your local DNS cache. You might also try to do a cache-flush as google.com. may have a form of negative cache entry that still is in the TTL period.

I don't think that the fact that the answers are non-authoritative should cause you problems here. This means that your DNS is not (globally or internet) authoritative, but it can still be authoritative for your own domain / zones.

If / when you do find the answer, please do post it here because I am rather curious as to the cause.

 

[jfhoffman3]

Honestly, I have tried everything that was posted and was unable to get it working. So I backed up all my data/settings and reloaded the system. issue was fixed. Rather strange problem??

 

[Noway2]

Odd yes, but not the first time I have seen such instances. I suspect that there was a non printable character or some other form of garbage somehwere in a config file or something. Dunno.

Glad to hear that you got it working at any rate.