DNS Setup - OK i’m lost.

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Well its not going well - the more I read the less I understand. Here
is the layout.

We have a small network with around 25 PC and 8 printers. All the PCs
(running XP Pro) and printers have the network settings set (no DHCPat
this time).
The PCs are set to:
Tcp/IP - 100.10.8.1 to 25
Subnet - 255.255.0.0
Dns - 100.10.10.3 & 100.10.10.4
Wins - 100.10.8.190 & 100.10.8.191

The NT4 Domain is called "ACCENT",
a PDC called "ENG_PDC", 100.10.8.191
a BDC called "ENG_BDC, 100.10.8.190
a File/Print server called "ENG_FILE", 100.10.8.192.


Every thing worked fine under NT4 - This past weekend I upgraded the
PDC to Server 2003. I have two new domain controllers and a new
file/print server I have installed Server2003 on that will replace the
existing hardware.
The new DCs will have adderss of: (two NICs in each machine)
ENGPDC - 100.10.8.170 and 100.10.8.171
ENGBDC - 100.10.8.172 and 100.10.8.173
ENGFILE - 100.10.8.174 and 100.10.8.175

So I set the new PDC up and the domain name became "ACCENT.eng". Now
when it came to the DNS I set up what I though would work (didn’t),
tried a few different setups (no working). At this point I am so
confused I don’t know what setting to use.

Since the PCs are using a DNS outside the local and is hardcoded, (if
my guess is correct) the DNS should only contain the server info.

Anyone have a starting point for me. Addition info needed?

Thanks

--
Posted using the http://www.windowsforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.windowsforumz.com/DNS-Setup-lost-ftopict418383.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.windowsforumz.com/eform.php?p=1396529

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

"the_tango" wrote:
> Well its not going well - the more I read the less I
> understand. Here is the layout.
>
> We have a small network with around 25 PC and 8 printers. All
> the PCs (running XP Pro) and printers have the network
> settings set (no DHCPat this time).
> The PCs are set to:
> Tcp/IP - 100.10.8.1 to 25
> Subnet - 255.255.0.0
> Dns - 100.10.10.3 & 100.10.10.4
> Wins - 100.10.8.190 & 100.10.8.191
>
> The NT4 Domain is called "ACCENT",
> a PDC called "ENG_PDC", 100.10.8.191
> a BDC called "ENG_BDC, 100.10.8.190
> a File/Print server called "ENG_FILE", 100.10.8.192.
>
>
> Every thing worked fine under NT4 - This past weekend I
> upgraded the PDC to Server 2003. I have two new domain
> controllers and a new file/print server I have installed
> Server2003 on that will replace the existing hardware.
> The new DCs will have adderss of: (two NICs in each machine)
> ENGPDC - 100.10.8.170 and 100.10.8.171
> ENGBDC - 100.10.8.172 and 100.10.8.173
> ENGFILE - 100.10.8.174 and 100.10.8.175
>
> So I set the new PDC up and the domain name became
> "ACCENT.eng". Now when it came to the DNS I set up what I
> though would work (didn't), tried a few different setups (no
> working). At this point I am so confused I don't know what
> setting to use.
>
> Since the PCs are using a DNS outside the local and is
> hardcoded, (if my guess is correct) the DNS should only
> contain the server info.
>
> Anyone have a starting point for me. Addition info needed?
>
> Thanks

as I can see you do not say what is not working nor what you want to
acchieve. What is the external DNS? Is that Dns - 100.10.10.3 &
100.10.10.4 ? What are these?

Setup DHCP to distribute IP addresses and options like DNS and WINS.
Configure the DNS/WINS options to point to the new servers. Configure
forwarding on the w2k3 dns servers to point to Dns - 100.10.10.3 &
100.10.10.4

does this help?

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

"Jorge_de_Almeida_Pinto" wrote:
> as I can see you do not say what is not working nor what you
> want to acchieve. What is the external DNS? Is that Dns -
> 100.10.10.3 & 100.10.10.4 ? What are these?
>
> Setup DHCP to distribute IP addresses and options like DNS and
> WINS. Configure the DNS/WINS options to point to the new
> servers. Configure forwarding on the w2k3 dns servers to point
> to Dns - 100.10.10.3 & 100.10.10.4
>
> does this help?

Sorry if I am unclear - let me see if I can do better.

Existing NT4 domain (called accent) with 1 PDC, 1 BDC, and 1
Print/File server.
Upgraded one DC to server 2003. -(Domain name used was ACCENT.eng)
Now running in MixedMode.
Trying to get the DNS on the 2003 DC setup.
Want to being online new PDC, BDC, F/P server and retire old hardware.

100.10.10.3 &100.10.10.4 are external DNS - these are in all of the
PCs since we do NOT use DHCP.

I saw no need for DHCP at this time since it was a small network and
all of the PCs already have static ip address.

We run WINS on the old NT4 and had a trust setup with another network
that was used to pass in addresses. The WINS isn’t working but I
though that getting the DNS working locally should be first.

"Configure the DNS/WINS options ----" That is my guestion.

Should I remove the Dns and Wins role from the 2003 box and start
over?
If so what goes whaer in the DNS setup? All the "forware", "reverse",
"_msdcc.ACCENT.eng" and "o-in-addr.arpa" stuff I don’t understand.

Thanks

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:3_1396529_2b32c72ce2ccd09f7f1370c61823b666@windowsforumz.com,
the_tango <UseLinkToEmail@WindowsForumz.com> made this post, which I then
commented about below:
> Well its not going well - the more I read the less I understand. Here
> is the layout.
>
> We have a small network with around 25 PC and 8 printers. All the PCs
> (running XP Pro) and printers have the network settings set (no DHCPat
> this time).
> The PCs are set to:
> Tcp/IP - 100.10.8.1 to 25
> Subnet - 255.255.0.0
> Dns - 100.10.10.3 & 100.10.10.4
> Wins - 100.10.8.190 & 100.10.8.191
>
> The NT4 Domain is called "ACCENT",
> a PDC called "ENG_PDC", 100.10.8.191
> a BDC called "ENG_BDC, 100.10.8.190
> a File/Print server called "ENG_FILE", 100.10.8.192.
>
>
> Every thing worked fine under NT4 - This past weekend I upgraded the
> PDC to Server 2003. I have two new domain controllers and a new
> file/print server I have installed Server2003 on that will replace the
> existing hardware.
> The new DCs will have adderss of: (two NICs in each machine)
> ENGPDC - 100.10.8.170 and 100.10.8.171
> ENGBDC - 100.10.8.172 and 100.10.8.173
> ENGFILE - 100.10.8.174 and 100.10.8.175
>
> So I set the new PDC up and the domain name became "ACCENT.eng". Now
> when it came to the DNS I set up what I though would work (didnâ?Tt),
> tried a few different setups (no working). At this point I am so
> confused I donâ?Tt know what setting to use.
>
> Since the PCs are using a DNS outside the local and is hardcoded, (if
> my guess is correct) the DNS should only contain the server info.
>
> Anyone have a starting point for me. Addition info needed?
>
> Thanks

Tango,

As Jorge asked, what exactly "does not work?"

First, do not multi-home your DCs or expect additional headaches to the
point that it may not work at all. I don't think you want to complicate this
procedure. Multihoming causes addtitional DNS entries that will cause
multple problems. If it's running RRAS or providing NAT, either use a member
server (non-DC) or a 3rd party hardware device to support that, such as a
really inexpensive DSL/Cable router to perform this function.

Second, what does this mean?
> Since the PCs are using a DNS outside the local and is
> hardcoded, (if my guess is correct) the DNS should only
> contain the server info.

Does that mean you are using an ISP's DNS address in ANY of your machines'
IP properties? If so, do not use that. Only use the internal DNS that
DCPROMO setup for you. That's the one hosing the accent.eng domain name.
With AD, ALL machines must only use the internal DNS server. That is how an
machine in AD "finds" the domain. Configure a forwarder for efficient
Internet resolution. If not sure how to configure a forwarder, see this
article.

323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003 :
http://support.microsoft.com/?id=323380

Keep in mind, NT4 DNS does not support AD's required SRV records. You need
to only use the 2003 DNS for all of your machines now since you've committed
to upgrading.


Here's additional reading you may find helpful:

Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003
Domain
http://support.microsoft.com/default.aspx?scid=kb;en-us;555040

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/?id=825036

291382 - Frequently asked questions about Windows 2000 DNS and Windows
Server 2003 DNS
http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

292822 - Name Resolution and Connectivity Issues on multihomed Windows 2000
or 2003 Domain Controller with Routing and Remote Access and DNS Installed
{DNS and RRAS and unwanted IPs registering]:
http://support.microsoft.com/?id=292822


Once again, do yourself a BIG favor, only use one NIC in each DC.

--
Regards,
Ace

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Infinite Diversities in Infinite Combinations.
=================================

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

the_tango <UseLinkToEmail@WindowsForumz.com> wrote:
> Well its not going well - the more I read the less I understand. Here
> is the layout.
>
> We have a small network with around 25 PC and 8 printers. All the PCs
> (running XP Pro) and printers have the network settings set (no DHCPat
> this time).
> The PCs are set to:
> Tcp/IP - 100.10.8.1 to 25
> Subnet - 255.255.0.0
> Dns - 100.10.10.3 & 100.10.10.4
> Wins - 100.10.8.190 & 100.10.8.191
>
> The NT4 Domain is called "ACCENT",
> a PDC called "ENG_PDC", 100.10.8.191
> a BDC called "ENG_BDC, 100.10.8.190
> a File/Print server called "ENG_FILE", 100.10.8.192.
>
>
> Every thing worked fine under NT4 - This past weekend I upgraded the
> PDC to Server 2003. I have two new domain controllers and a new
> file/print server I have installed Server2003 on that will replace the
> existing hardware.
> The new DCs will have adderss of: (two NICs in each machine)
> ENGPDC - 100.10.8.170 and 100.10.8.171
> ENGBDC - 100.10.8.172 and 100.10.8.173
> ENGFILE - 100.10.8.174 and 100.10.8.175

DCs should not be multi-homed, especially since both NICs are on the same
subnet, you can use NIC teaming software or since this is Win2k3 you can
bridge the NICs, giving the Bridge only one IP address.

>
> So I set the new PDC up and the domain name became "ACCENT.eng". Now
> when it came to the DNS I set up what I though would work (didn’t),
> tried a few different setups (no working). At this point I am so
> confused I don’t know what setting to use.

If I'm getting this right, you have upgraded the NT4 PDC, and set up two
additional replica DCs (The term BDC is no longer valid in Active Directory,
there are no BDCs).
DNS is a requirement for Active Directory and all members and replica DCs
must use the local DNS server, you should install DNS on all DCs and use
Zones stored in Active Directory, then the zones will replicate themselves
to all DCs. The correct settings for each DC should be that all DCs should
use the first DC as its preferred DNS, then one of the other DCs as it
alternate DNS server. If you should use a third DNS server in the list, it
may use itself. This assures the when the DC is starting up, it has a DNS
server in its list that is already running. (Unless all DCs are turned off
simultaneously, which I would not advise) This prevents startup errors when
you start up a DC, without a DNS server available.

> Since the PCs are using a DNS outside the local and is hardcoded, (if
> my guess is correct) the DNS should only contain the server info.

This will NOT work, all member clients must use the DC's address for DNS
only. The DNS service on the DC will resolve all DNS names for the clients.
Here are some KB articles you should become very familiar with.
825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036&sd=RMVP

323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;323380&sd=RMVP

DNS query responses do not travel through a firewall in Windows Server 2003:
http://support.microsoft.com/default.aspx?scid=kb;en-us;828263&sd=RMVP

Frequently asked questions about Windows 2000 DNS and Windows Server 2003
DNS
http://support.microsoft.com/default.aspx?scid=kb;en-us;291382



--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================