Click to See Complete Forum and Search --> : nslookup defaults to 127.0.0.1


McEve
10-20-2002, 07:15 PM
I have a win2000 server, one of 2 DC's.

The KBarticle Q172060 describes my problem, but we do have a DNS server configured for the computer....

ping localhost returns 127.0.0.1 - fine..
ping <hostname> returns 127.0.0.1 - not so fine

nslookup:

*** Default servers are not available
Default Server: UnKnown
Address: 127.0.0.1

____________

nslookup <hostname>
*** Default servers are not available
Server: UnKnown
Address: 127.0.0.1

Name: <hostname>.qdomain.questus.no
Address: 192.168.0.45

____________

nslookup <hostname> <dns server>
Server: <dns server>.qdomain.questus.no
Address: 192.168.0.50

Name: <hostname>.qdomain.questus.no
Address: 192.168.0.45

____________

Netdiag

Failed to get information for a network adapter. The error occurred was: The pipe is being closed.
(232)[FATAL] Cannot find TCP/IP configuration from the registry.

_____________

It seems to me that the computer defaults to using 127.0.0.1 for nameresolution.... why..?


ping www.whitehouse.org
Unknown host www.whitehouse.org.


But it still resolves other hosts on the local network:


ping <hostname1>

Pinging <hostname1> [192.168.0.13] with 32 bytes of data:

Reply from 192.168.0.13: bytes=32 time<10ms TTL=128
Reply from 192.168.0.13: bytes=32 time<10ms TTL=128
Reply from 192.168.0.13: bytes=32 time<10ms TTL=128
Reply from 192.168.0.13: bytes=32 time<10ms TTL=128

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

This host is on the LAN as you can see.

Anybody know what's going on with this DC?

McEve

10-23-2002, 04:00 PM
Check the settings for the static IP of the DC.
1. make sure it points to the correct DNS server
2. try checking the box under advanced to register this computers connection with DNS
3. make sure the host name is approiate for the domain (localhost.domain.com) under the network ID full computer name If this is incorrect hit more and correct the DNS suffix
4. Try using ipconfig /registerdns
5. Check the DNS server to make sure it has entries for that DC, make sure dynamic update is enabled for both foward and reverse look up zones and that they are AD integrated if applicable.
6. Restart the netlogon service and check for the DNS entry again.

Those are the only things I can think of off hand, you may also want to test the physical connection to the DNS server with straight IP pings to make sure the packets are reaching the DNS server.


------------
McEve at 10/20/2002 8:15:11 PM


I have a win2000 server, one of 2 DC's.

The KBarticle Q172060 describes my problem, but we do have a DNS server configured for the computer....

ping localhost returns 127.0.0.1 - fine..
ping <hostname> returns 127.0.0.1 - not so fine

nslookup:

*** Default servers are not available
Default Server: UnKnown
Address: 127.0.0.1

____________

nslookup <hostname>
*** Default servers are not available
Server: UnKnown
Address: 127.0.0.1

Name: <hostname>.qdomain.questus.no
Address: 192.168.0.45

____________

nslookup <hostname> <dns server>
Server: <dns server>.qdomain.questus.no
Address: 192.168.0.50

Name: <hostname>.qdomain.questus.no
Address: 192.168.0.45

____________

Netdiag

Failed to get information for a network adapter. The error occurred was: The pipe is being closed.
(232)[FATAL] Cannot find TCP/IP configuration from the registry.

_____________

It seems to me that the computer defaults to using 127.0.0.1 for nameresolution.... why..?


ping www.whitehouse.org
Unknown host www.whitehouse.org.


But it still resolves other hosts on the local network:


ping <hostname1>

Pinging <hostname1> [192.168.0.13] with 32 bytes of data:

Reply from 192.168.0.13: bytes=32 time<10ms TTL=128
Reply from 192.168.0.13: bytes=32 time<10ms TTL=128
Reply from 192.168.0.13: bytes=32 time<10ms TTL=128
Reply from 192.168.0.13: bytes=32 time<10ms TTL=128

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

This host is on the LAN as you can see.

Anybody know what's going on with this DC?

McEve