Windows Server

B · Guest

New domain, Windows 2003 server first controller built (call it DC1).
Has DNS, which is working fine. Clients can resolve names, etc.
Created a new 2000 server (NOT a DC) with DNS (call it S1). It appears
to be functioning fine as a secondary DNS server, however, we have a
couple of questions:

1. when we go to the DNS console on the 2000 server and click it in the
left pane, the right pane gives us the text "Configure the DNS Server",
as if it's not configured. But in the left pane I can navigate down to
our AD zone, see PCs that have been added to the domain, etc. is this
behavior normal?

2. in the properties of the network interface on S1, I can't put
127.0.0.1 in as the DNS server (but I was able to on the primary or
first DNS server). I get a pop up error message box stating "IP
addresses starting with 127 are not valid..." so, for this server,
should it have the loopback address in the network properties DNS box,
or should it have the primary DNS server (DC1), or should it have it's
own IP address?

3. should I enable forwarders on this server S1, and if so, should I
forward to the primary DNS server (DC1), or should I forward to our ISP
DNS (as the primary is set up)?

4. on the primary (DC1), I can't connect to the secondary (S1) by name
to manage under DNS - I get "The server is unavailable. would you like
to add it anyway?". I reply yes, the server is added to the left pane,
but I can't manage it. When I go to the management console on S1, I
see right off the bat both DC1 and S1. is this normal? can a primary
not manage its secondary?

TIA for any and all help.

Kevin D. Goodknecht Sr. [ · Guest

B <barmand@amphenolpcd.com> wrote:

B · Guest

OK, here we go:

1. it appears that the person who configured the server may have
finished the configuration through Remote Desktop Terminal Server, and
then didn't log out of the session. I say this because the Configure
your server window came up (the window you first get when Windows 2000
server is done configuring). I selected One or more servers are
already running in my network. This is interesting because this was
already done by the person who set it up (see Terminal Services,
above), and the server already showed up as a domain member - we sign
on to it with domain admin privledges

In any case, I then went through the DNS wizard again, and at the end I
got an error message stating it was already configured, so I clicked
OK, and then it really was set up and the Configure the DNS Server text
is gone from the right pane.

4. to connect to the server ("S1") from the primary DNS server to
manage it, I couldn't connect just by using the name S1 (even though S1
appears in both DNS and WINS). I had to connect to it by
S1.domainname.local (domainname.local being our new AD domain).

All appears to be normal now.

Thanks for your help Kevin.

SIME U via WinServerKB.co · Guest

Hi

If "domainname.local" is in the DNS suffix search list should S1 not resolve
via DNS without having to use the FQDN ? Is "append primary and connection
specifiDNS suffix" selected on the NIC TCPIPproperties?

S

B wrote:

B · Guest

"append primary and connection specifiDNS suffix" is indeed selected on
the NIC TCPIP properties. however, this morning I went to the dnsmgmt
on DC1, deleted the server s1.domainname.local from the left pane, and
then connected to the server by just the name S1 and it worked. So,
maybe it took a little time for the two servers to square up the DNS
info and all is well now.

In any case, it all seems fine and there are other fires to put out.

Thanks for your help.
Brian

	Windows Server Forum Index -> DNS	All times are GMT
Page 1 of 1