Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unable lookup server

Status
Not open for further replies.

tming

Technical User
Dec 19, 2001
40
0
0
HK
I don't know my question if post in this forum or not.

I have two Windows 2003 servers.
ServerA is DC, ServerB is goning to join the Domain in ServerA
DNS is on ServerA
Both of them are in different subnet.
In ServerB i use nslookup to lookup the ip by typing the ServerA or ServerB host name, it cannot resolve.
But i use IP address the DNS server can resolve.
I can telent to the ServerA port 53.
Both servers can be reached by tracert command.
What is the problem?
 
on both servers, flush and register your dns and reload your table..

from the command prompt.

ipconfig /flushdns
then
ipconfig /registerdns
then
nbtstat -R

make sure you use the captial R and not lower case..

then try and resolve. if not..

in the tcp/ip properties of your NIC

make sure that the DNS setting are correct and under advanced>DNS tab
select resolve is order of list,
add in you domain FQDN..

ie.. domain.local etc..

try again.. another dns flush/register would not do any harm..
 
Thanks first. It can be lookup now.

But what does this means when i join the server
"The domain name might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS"
Is Windows 2000 or above only need DNS for resolvation?
Why it seems that i need a WINS.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top