Re: new administrator..why DNS?
- From: "Kevin D. Goodknecht Sr. [MVP]" <admin@xxxxxxxxxxxxxx>
- Date: Wed, 15 Jun 2005 11:22:16 -0500
In news:ODNFeqbcFHA.228@xxxxxxxxxxxxxxxxxxxx,
Sarah Sanders <sysadmin@xxxxxxxxxxxxxxx> posted this:
> Hello All-
>
> I am a new administrator just out of school and I am having trouble
> understanding the reason for having my server configured as a DNS
> server.
>
> I just set up a new domain on the server at work. I first configured
> my server as a TS server because we are going to run our point of
> sale program through terminal services. I have licenses and
> everything set up OK.
>
> I then installed active directory because I want to set up users and
> control access/permissions the correct way. When I set up active
> directory it asked me to set up the server as a DNS server. I don't
> need this, at least I don't think. But then I bought a book and it
> said that I need DNS running in order to use Active Directory?????
Yes, you need DNS for Active Directory. It is recommended to run DNS on the
DC and use only its address for DNS on all member clients.
>
> I have an off-site web server with a separate company to manage our
> internet domain, and besides, it's a totally separate domain name. I
> set up our Server 2003 domain as a .local one, as the book suggested.
> We use a cable modem to connect to the internet and we have a small 4
> pt router and a switch. DHCP is set up on the router so all the
> clients are assigned addresses through that. I want to continue to
> use it just like it is. I use the ISP's DNS servers.
You cannot use the ISP DNS, you can only use them as a forwarder.
>
> My question is, why do I need this set up as a DNS server? It seems
> like more confusion than I need right now.
Domain Controllers store their service location (SRV) records in DNS and how
all clients locate domain controllers and other services needed for Active
Directory, (LDAP, Global Catalog, Kerberos etc) The DC will attempt
registration of these records in the DNS servers listed in TCP/IP
properties.
It is really very simple, install DNS on the DC if it is not already. Create
a Forward Lookup zone for the same name as the AD domain in ADU&C. Set the
zone to allow dynamic updates so the DC can register its records. Use the
DC's IP address (even if you only have one DC) for DNS on the DC and all
member clients.
Then, run this command in a command prompt on the DC:
net stop netlogon & net start netlogon & ipconfig /flushdns & ipconfig
/registerdns
This will register all the DCs records and greatly improve the performance
problems you are having but didn't elude to, (such as startup and logon
taking 15 - 20 minutes).
--?
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
===================================
.
- Follow-Ups:
- Re: new administrator..why DNS?
- From: Sarah Sanders
- Re: new administrator..why DNS?
- References:
- new administrator..why DNS?
- From: Sarah Sanders
- new administrator..why DNS?
- Prev by Date: Re: new administrator..why DNS?
- Next by Date: MX records A records and email
- Previous by thread: Re: new administrator..why DNS?
- Next by thread: Re: new administrator..why DNS?
- Index(es):
Relevant Pages
|