Lets start with http://www.google.com is at 208.67.219.231
see for yourself http://208.67.219.231/

now then, my ipconfig /all reports[indent:2588ne5t]Windows IP Configuration
Host Name . . . . . . . . . . . . : ltbeard
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : socal.rr.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : socal.rr.com
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Eth
ernet NIC
Physical Address. . . . . . . . . : 00-xx-yy-3D-zz-00
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.222.220
Primary WINS Server . . . . . . . : 192.168.0.4
Lease Obtained. . . . . . . . . . : Wednesday, April 22, 2009 8:29:17 AM

Lease Expires . . . . . . . . . . : Monday, January 18, 2038 8:14:07 PM[/indent:2588ne5t]
(yes, the DNS addresses are for the OpenDNS servers but the symptom below was present even with the original ISP dns addresses)

First, ping http://www.google.com works well as does the http: shown above.
HOWEVER,
[sample:2588ne5t]C:\Documents and Settings\Jeff>nslookup http://www.google.com
Server: resolver1.opendns.com
Address: 208.67.222.222

Non-authoritative answer:
Name: http://www.google.com.socal.rr.com
Address: 208.67.216.132[/sample:2588ne5t]the addition of the suffix forces the lookup to return
an address related to the DNS: 208.67.216.132

(use the default DNS addresses and the same thing happens).

substitute the google ip addres and we get a reasonable reply[sample:2588ne5t]C:\cygwin\home\Jeff>nslookup 208.67.219.231
Server: resolver1.opendns.com
Address: 208.67.222.222

Name: google.navigation.opendns.com
Address: 208.67.219.231[/sample:2588ne5t]

NSLOOKUP is bypassing the resolve mechanism whereas ping and everyone else
applies it correctly, even a perl script [sample:2588ne5t]C:\cygwin\home\Jeff>iplookup.pl http://www.google.com
http://www.google.com -> 208.67.219.231 which is correct[/sample:2588ne5t]

I believe that the Connection-specific DNS Suffix . : socal.rr.com is causing the issue,
but can't seem to get it removed sucessfully. This has been a long standing issue which
I've just ignored (btw: which also prompted the writing of the iplookup.pl script ).

Anyone with ideas?
The proper response from nslookup domain.name -> is the ip address assigned that domain

__________________
J. O. Beard; you + tech-101.com => synergism. Secure your system now

I think I understand. This is not my strongest subject

Nslookup will always devolve the name from the current context. If you fail to fully qualify a name query (that is, use trailing dot), the query will be appended to the current context.

In your example, the current DNS settings are social.rr.com and a query is performed on http://www.google.com; the first query will go out as http://www.google.com.social.rr.com because of the query being unqualified.

The trailing dot makes the domain name absolute and technically unambiguous. No software is expected to append anything to such a domain name when looking it up in DNS. With the absence of the trailing dot, some software may theoretically attempt to append one or more suffixes and the consequences can range from harmless redundant lookups to potentially dangerous lookups of things that are not meant to be looked up.

I believe you can simply use a Fully Qualified Domain Name (that is, add the trailing dot to the name).

__________________
__________________
Check us out on Facebook!

Useful Guides: Networking 101 Security 101 Disable Real Time Monitoring Virus/Malware Preliminary Removal Instructions

UNBELIEVABLE! Now teach me where you found or got this insight!!!

case #1[sample:3l40d2ep]C:\Documents and Settings\nMaster>nslookup http://www.google.com.
Server: resolver1.opendns.com
Address: 208.67.222.222

Non-authoritative answer:
Name: google.navigation.opendns.com
Addresses: 208.67.219.231, 208.67.219.230 << real google.com addresses
Aliases: http://www.google.com[/sample:3l40d2ep]
case #2[sample:3l40d2ep]C:\Documents and Settings\nMaster>nslookup http://www.google.com
Server: resolver1.opendns.com
Address: 208.67.222.222

Non-authoritative answer:
Name: http://www.google.com.socal.rr.com
Address: 208.67.216.132 << part of OpenDNS [/sample:3l40d2ep]

__________________
J. O. Beard; you + tech-101.com => synergism. Secure your system now

I don't know for sure. I had notes on it from various sites, because i was having DNS problems a while back.

__________________
__________________
Check us out on Facebook!

Useful Guides: Networking 101 Security 101 Disable Real Time Monitoring Virus/Malware Preliminary Removal Instructions