Oh My God! DNS again.

[Cheuk Man]

I have to reconfigure a w2k network with single forest
single domain. There are two DCs: server1 and server2.
Both installed with AD & DNS. When I perform simple and
recursive DNS query to test both server, recursive query
failed on both servers. When I perform nslookup with my
w2k pro workstation, the results are as follows:

(Primary DNS set to server1)
============================
C:\>nslookup
*** Can't find server name for address <ip-server1>: Non-
existent domain
Default Server: server2.acme.com
Address: 10.20.0.8

C:\>nslookup mypc
*** Can't find server name for address <ip-server1>: Non-
existent domain
Server: server2.acme.com
Address: 10.20.0.8

Name: mypc.acme.com
Address: 10.20.50.21

(Primary DNS set to server2)
============================
C:\>nslookup
Default Server: server2.acme.com
Address: 10.20.0.8

C:\>nslookup mypc
Server: server2.acme.com
Address: 10.20.0.8

Name: mypc.acme.com
Address: 10.20.50.21

When I go to DNS console on both servers and select them,
I can see on the right pane that the system report both
servers have not configured yet. I can see "Configure the
server" when I right-click server1 or server2 in DNS
console.

My questions are:
(1) How can I re-configure one server to be the root
server (no dot zone required)with correct forward lookup
zones?

(2) How should I configure reverse lookup zone if my
network consists of two subnets 10.20.0.0 and 10.30.0.0?

I am lost now and appreciate if anyone could give me some
hints and advice.

Warmest regards,
Cheuk Man

 

[Herb Martin]

I have to reconfigure a w2k network with single forest
single domain. There are two DCs: server1 and server2.
Both installed with AD & DNS. When I perform simple and
recursive DNS query to test both server, recursive query
failed on both servers. When I perform nslookup with my
w2k pro workstation, the results are as follows:

(Primary DNS set to server1)
============================
C:\>nslookup
*** Can't find server name for address <ip-server1>: Non-
existent domain
Default Server: server2.acme.com
Address: 10.20.0.8

C:\>nslookup mypc
*** Can't find server name for address <ip-server1>: Non-
existent domain
Server: server2.acme.com
Address: 10.20.0.8

Name: mypc.acme.com
Address: 10.20.50.21

(Primary DNS set to server2)
============================
C:\>nslookup
Default Server: server2.acme.com
Address: 10.20.0.8

C:\>nslookup mypc
Server: server2.acme.com
Address: 10.20.0.8

Name: mypc.acme.com
Address: 10.20.50.21

When I go to DNS console on both servers and select them,
I can see on the right pane that the system report both
servers have not configured yet. I can see "Configure the
server" when I right-click server1 or server2 in DNS
console.

My questions are:
(1) How can I re-configure one server to be the root
server (no dot zone required)with correct forward lookup
zones?

Root in DNS means a DOT zone -- just make it like any
other zone -- IF you really need that.

If you only have one Domain/Zone, you (almost certainly)
don't need a "." dot zone.

Just configure the forwarder that can resolve the Internet
(on the forwarding tab) -- probably to your ISP.

(2) How should I configure reverse lookup zone if my
network consists of two subnets 10.20.0.0 and 10.30.0.0?

Do you even need it?

Just make the 10.in-addr.arpa zone (or both the 20.10.in-addr.arpa
and the 30.10.in-addr.arpa) and add records there as needed.

Since there won't be any machines OUTSIDE of the 10.20 & 10.30
you can just use the whole 10.net

If you want dynamic reverse records you must enable dynamic
updates on these in addition to your forward zone -- remember,
to DNS a forward and a reverse zone are UNRELATED -- the
fact that humans see a relationship is just a coincidence (to DNS).

I am lost now and appreciate if anyone could give me some
hints and advice.

You only have one Domain with Zone -- make the forward zone.
Set Forwarders to you ISP's (or other suitable) DNS sever(s)
that can resolve the Internet.

Add reverse zones IF you feel they are necessary. The best
reason for reverse zones are to keep your machines from "going
to the Internet" for the private address ranges.

In that case you really should have reverse zones for all of the
10.net, the 192.168.net and the 16 nets from 172.16.net to
172.31.net.

 

[Jonathan de Boyne Pollard]

CM> C:\>nslookup
CM> *** Can't find server name for address <ip-server1>: Non-existent domain

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/nslookup-daft-error-message.html>

CM> (Primary DNS set to server1)
CM> [...]
CM> Name: mypc.acme.com
CM> Address: 10.20.50.21
CM> (Primary DNS set to server2)
CM> [...]
CM> Name: mypc.acme.com
CM> Address: 10.20.50.21

You are asking how to go about various things, in pursuit of
addressing a problem, but haven't actually demonstrated the
existence of an actual problem. What is the actual problem ?

<URL:http://perl.plover.com./Questions3.html>

CM> (1) How can I re-configure one server to be the root
CM> server (no dot zone required) [...] ?

A "root server" _is_, pretty much by definition, a server
with a "." "zone".

CM> (2) How should I configure reverse lookup zone if my
CM> network consists of two subnets 10.20.0.0 and 10.30.0.0?

Use a "10.in-addr.arpa." "zone". The whole 10.*.*.* network is
reserved for non-public use, and you must yourself handle the
address->name lookup for all of it. The fact that right now you
only actually use some of the available addresses is irrelevant.

 

[Larry Brasher]

Hello Cheuk,

What you are seeing is common when you do not have a reverse lookup zone
created.

"Can't find server name for address <ip-server1>: Non-existent domain"

The below listed links explains this somewhat.
http://support.microsoft.com/default.aspx?scid=kb;en-us;242906
http://support.microsoft.com/default.aspx?scid=kb;en-us;200525

"This error occurs when there is no PTR record for the name server's IP
address. When Nslookup.exe starts, it does a reverse lookup to get the name
of the default server. If no PTR data exists, this error message is
returned. To correct make sure that a reverse lookup zone exists and
contains PTR records for the name servers."

Despite the fact that you see this message at the command prompt, if you
would query for your domain records you will probably get a response.

example:
set q=any (press enter)
<domain name> (press enter)

You will see a listing of DNS records.

Mr. Martin is right, if you were to create a reverse lookup zone, this
error should go away.

Shane Brasher
MCSE (2000,NT),MCSA, A+
Microsoft Platforms Support
Windows NT/2000 Networking