Thanx,
I think I need to start wearing my glasses he say's sheepishly. Guess 174 is
not close enough to 172. :^)
Regards
Bob
-----Original Message-----
From: Roger Seielstad [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 11:03 AM
To: NT System Admin Issues
Subject: RE: DNS issues
What that's saying is that your client machine can't connect to the DNS
servers with the following IP's:
206.174.3.100
206.174.3.101
206.174.3.98
206.174.3.99
but it is succeeding on 206.172.3.100.
You've got the wrong DNS settings on the machine you're on.
------------------------------------------------------
Roger D. Seielstad - MCSE MCT
Senior Network Administrator
Peregrine Systems
Atlanta, GA
http://www.peregrine.com
-----Original Message-----
From: Bob Cheeseman [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 7:56 AM
To: NT System Admin Issues
Subject: DNS issues
We recently changed upstream providers, and since that time are getting the
error below. It kind of weird considering that all 4 name servers time out
yet the last 3 lines return the correct result. Any thoughts on where I
should start looking.
C:\>nslookup www.ips-can.com
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 206.174.3.100: Timed out
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 206.174.3.101: Timed out
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 206.174.3.98: Timed out
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 206.174.3.99: Timed out
Server: web1.kingkom.com
Address: 206.172.3.100
Name: web1.ips-can.com
Address: 206.172.3.100
Aliases: www.ips-can.com
Regards
Bob Cheeseman
King Kommunications
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
