configuring internal and external dns

[antonio chua]

hello. I'm running win2k advance server and several winxp
prof. after installing dns and running dcpromo in 2k,
everything seems ok. I can ping the name of the server as
well as the ip address. netdiag and dcdiag gives passed
results likewise. nslookup shows the dns server, but
nslookup followed by the server name failed. I
received "none existent domain".

when I try nslookup on xp machines followed by the server
name, again, it says "cannot find address etc."

while searching solutions on the web, i think my problem
is about bad configuration of DNS.

2k is configured for internal used but I am also using it
to connect to the internet. how can I configure external
dns?

we're in the business of lan and internet gaming. so I
want 2k to be used as that: for lan and internet. is that
possible? Can anyone tell me how to do it?

 

[Kevin D. Goodknecht [MVP]]

In

hello. I'm running win2k advance server and several winxp
prof. after installing dns and running dcpromo in 2k,
everything seems ok. I can ping the name of the server as
well as the ip address. netdiag and dcdiag gives passed
results likewise. nslookup shows the dns server, but
nslookup followed by the server name failed. I
received "none existent domain".

when I try nslookup on xp machines followed by the server
name, again, it says "cannot find address etc."

while searching solutions on the web, i think my problem
is about bad configuration of DNS.

2k is configured for internal used but I am also using it
to connect to the internet. how can I configure external
dns?

we're in the business of lan and internet gaming. so I
want 2k to be used as that: for lan and internet. is that
possible? Can anyone tell me how to do it?

What you are seeing when you start nslookup is not really an error and is
not a big problem. When nslookup starts it performs a reverse lookup on the
IP is pointing to. IF there is no reverse lookup zone or PTR record for the
IP it is pointing to nslookup gives you the message, which usually freaks
people out and gives you the impression that DNS is not working. After you
see the message try running a lookup on a known good name (i.e.
microsoft.com) to verify that DNS is working.
If you will configure a reverse lookup zone and PTR record the message will
stop and give you the name of the PTR record you created.

 

[Michael Johnston [MSFT]]

If queries in NSLOOKUP are failing for the host name of the server, the problem is with the DNS suffix on the client. Verify that the
primary DNS suffix on the XP client matches that of your AD domain name. To find the primary DNS suffix, right click on My
Computers and choose propertise. Click on the Computer name tab, then click Change and then click More. This will open the
DNS Suffx window. The DNS suffix should match that of your domain name.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.