Re: setup/configure internal domain dns server?



On Jul 3, 1:17 pm, "Danny Sanders" <DSand...@xxxxxxxxxxxxxxx> wrote:
How should I go about configuring the dns server on the main domain
controller? Is there a quide for such a process for just a small
internal network? Currently the clients on the domain just point to
the ISP provided dns servers and not the main domain controller but I
don't believe that thats the appropriate way to continue forward.

AD must have a DNS server setup for the AD domain. Basic AD DNS setup is
install DNS on a server to host the DNS zone for the AD domain. Point the
DNS server to itself for DNS, use the actual IP address not 127.0.0.1.
See:http://support.microsoft.com/kb/814591/en-us

Point all AD clients to the DNS server setup for the AD domain ONLY (Servers
are AD clients also) Pointing an ad client to a DNS server not setup to host
your DNS zone (Example would be your ISP's DNS server) as preferred will
cause long log in times. Pointing your AD clients to any DNS server not
setup to host the DNS zone for your AD domain as alternate will cause
network drives to become inaccessible after a time.
See:http://support.microsoft.com/kb/825036/en-us

For Internet access configure the DNS server to forward requests and list
your ISP's DNS servers as the forwarder (or use root hints). This is the
only place on an AD domain where your ISP's DNS server should be listed.
See:http://support.microsoft.com/kb/323380/en-us

Should I setup the domain controller as a dhcp server as well?

If you want to or you can provide static IP addresses for your AD clients.
It's not "mandatory" that the DC is the DHCP server. The Important part is
that the DHCP server hand out the correct DNS server for the AD domain. That
would be the DNS server setup for the AD domain.

hth
DDS

<kamu...@xxxxxxxxx> wrote in message

news:1183483570.694734.285910@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hello,

I work at a small business and we have deployed a windows 2003 server
environment with XP clients.

Due to my inexperience I've setup a functional domain but am
experiencing some issues. I'm trying to add in a backup domain
controller but the new server says that dns is configured incorrectly
on the main dns server. (Since we lack the funds to have many servers
the primary domain controller is also acting as a dns server but
clearly I've not configured it properly.)

Our ISP provides us with a 4 port router with static ips. I've
assigned 1 static IP to a wireless router which acts as our dhcp
server. The domain controller is connected (hardwired) to that
wireless router and then the clients connect to the router
wirelessly.

How should I go about configuring the dns server on the main domain
controller? Is there a quide for such a process for just a small
internal network? Currently the clients on the domain just point to
the ISP provided dns servers and not the main domain controller but I
don't believe that thats the appropriate way to continue forward.

Should I setup the domain controller as a dhcp server as well? How
should routing be setup for an environment like this? Should the ISP
provided router give a static IP to the domain controller on one nic
and then the 2nd nic be conencted to the wan port on the wireless
router to provide ips for the wireless clients?

I'm at a loss as to how to continue forward seeing as in our current
setup things 'work' but I know that it definitely isn't an ideal
scenario. Any help/suggestions would be much appreciated and thanks
in advance for taking the time to take a gander at what is probably a
very simple/easy solution.

Kamuiiv

Thanks for the information. I'll try out your suggestions and read up
on the provided links.

.



Relevant Pages

  • Re: AD clients can no longer connect to DC in 2003
    ... perhaps you should look at the clients. ... Verify that the clients are pointing to an existing, internal DNS server ... However it does not prove that the correct SRV records are present. ... >net start netlogin>>That should get logins going again. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Logon Win2000
    ... the XP Pro computers must point only to the AD domain controller for dns. ... any ISP dns servers as a preferred dns server on any W2K/XP Pro domain computers. ... > In My Xp clients I configure the clients to log on in the AD server. ...
    (microsoft.public.win2000.group_policy)
  • Re: nslookup
    ... and switch to NetBIOS resolution so you cannot be sure what you ... NSLookup will NOT use the built-in name cache nor the hosts file NOR ... DNS server to check so you can determine if SOME DNS server is working ... servers are hosting dhcp successfully giving IP's to clients. ...
    (microsoft.public.windows.server.dns)
  • RE: NT to AD upgrade question (advanced)
    ... The DNS Server that is in the DMZ, ... I cannot manually change the DNS setting on the clients. ... transfers the AD Integrated zone from the DC. ...
    (microsoft.public.windows.server.migration)
  • Re: setup/configure internal domain dns server?
    ... the ISP provided dns servers and not the main domain controller but I ... AD must have a DNS server setup for the AD domain. ... DNS server to itself for DNS, use the actual IP address not 127.0.0.1. ... Point all AD clients to the DNS server setup for the AD domain ONLY (Servers ...
    (microsoft.public.windows.server.dns)