?
Solved

Wrong IP address Default DNS Server

Posted on 2006-04-28
13
Medium Priority
?
1,161 Views
Last Modified: 2012-06-22
I am running a AD integrated Domain controller.  DNS on the server points to itself for resolution as primary and another DC for secondary.  When I perform nslookup, I run into the following error.

DNS request timed out.
    timeout was 2 seconds.
*** Can't find server name for address 192.168.50.2: Timed out
Default Server:  UnKnown
Address:  192.168.50.2

The server's address is actually 192.168.50.3 and am running DNS services.  I've search all over looking for the place to force the default dns server ip to the correct one.  Can some point me in the right direction?  Thanks
0
Comment
Question by:chunger
  • 3
  • 3
  • 2
  • +4
12 Comments
 
LVL 25

Expert Comment

by:mikeleebrla
ID: 16565741
check the reverse DNS,,, make sure you have a record for 192.168.50.2
0
 

Author Comment

by:chunger
ID: 16565746
I do, but it is not the server with DNS on it anymore.  192.168.50.3 is the correct server and it is in reverse dns.
0
 
LVL 51

Expert Comment

by:Netman66
ID: 16565815
If you are using DHCP to assign addresses, check the Scope and the Server options in DHCP MMC to make sure the proper DNS server IP is being given out.

0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 51

Expert Comment

by:Netman66
ID: 16565817
It should be option 005 and 006.

0
 
LVL 1

Expert Comment

by:ChadHooper
ID: 16567216
Check the DNS entries under the TCP/IP configuration on the server. When running nslookup, the program uses the 'Preferred DNS server' of the local machine. If I understand correctly what you've said above, then it is just a typo in the IP settings. If I've misunderstood what you've said above, apologies in advance!
0
 

Author Comment

by:chunger
ID: 16569334
The issue I am having is on the server running dns and dhcp.  The clients are receiving the correct dns server address of 192.168.50.3.  The server's primary dns is itself 192.168.50.3.
When running nslookup, it tries to use the old server ip address of 192.168.50.2 as the default dns server.
The reason, I am trying to correct this is because I am noticing some browsing issues when trying to browse my 192.168.49.x network across town.  Thanks
0
 
LVL 5

Expert Comment

by:mickinoz2005
ID: 16569702
Go into DNS on the server and look through the DNS config you will many references to the server and PDC AND other options you must go through all branches on the tree and see if it is holding an old reference to itself.

so go to start / admin tools / DNS and expand your dns go to forward lookup zones and then go through expanding all the branches if you see 192.168.50.2 anywhere delete the entry.

Also do a ipconfig /flushdns and an arp -d just to clear them too.

It is most likely that there is still a reference to the .2 address in your DNS.

Michael
0
 
LVL 14

Expert Comment

by:canali
ID: 16573932
You need a ptr record

http://support.microsoft.com/kb/242906/en-us

where xxx.xxx.xxx.xxx is the Internet Protocol (IP) address of the host on which you are attempting to start Nslookup.
CAUSE
When Nslookup starts, it attempts to resolve the IP address of its host's DNS server to its fully qualified domain name (FQDN). If the DNS server does not respond or if the DNS server's reverse lookup zones do not contain a PTR record for the DNS server's IP address, the error message is displayed.
RESOLUTION
If the host is configured to point to itself for DNS name resolution, verify that the DNS service is starting without error and that a PTR record exists in the appropriate reverse lookup zone.

You can manually create the PTR record if your DNS server does not have dynamic updates enabled. If dynamic updates are enabled, you can create the PTR record by typing the following command at a command prompt:
ipconfig /registerdns
0
 
LVL 5

Expert Comment

by:mickinoz2005
ID: 16576793
Why would a ptr have anything to do with a mismake in his DNS. It is not that it is not resolving it is resolving to the wrong / old address. By not removing this address he could potentially have many further problems with DNS.

Michael
0
 
LVL 51

Expert Comment

by:Netman66
ID: 16577006
Any entry in DNS that points to the correct servername with the wrong (old) IP address will cause problems.  Remove all entries in every container in DNS that refers the servername to the wrong IP.

0
 

Author Comment

by:chunger
ID: 16685082
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\{49896D9D-40A3-46CA-9079-6B5CADF807B4}\Parameters\Tcpip
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{96D7F60D-5F32-4E96-9E5D-726388741448}

The old IP address had to be edited in the above registry keys to resolve the problem.  Thanks all for the help.
0
 

Accepted Solution

by:
CetusMOD earned 0 total points
ID: 16876066
PAQed with points refunded (250)

CetusMOD
Community Support Moderator
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Learn about cloud computing and its benefits for small business owners.
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.

621 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question