whats the story on DHCP/DNS?

IN my net+ studies i learned that a DNS server resolves Names I/E www.techexams.net to IP address's. Now that I have set up my server at home, I am learning i need to install DNS so that my server can issue ip address's to my clients.. I thought thats what DHCP did?

Thanks for the comments

pandimus

Find more posts tagged with

Comments

cheeblie

DNS is not to issue IP addresses to clients. You need to install DNS because it is required by Active Directory.

Cheeblie

pandimus

Ok.. That sounds resonable.. But why is it that active directory needs DNS?

Webmaster

Active Directory Domain needs Domain Naming System

And, the DHCP server needs to be authorized in ADS. As you can see it is all 'connected'. This is the primary difference between NT 4 and 2000 domains. NT 4 relies on NETBIOS/WINS, 2000 on DNS.

pandimus

So DNS in a domain does the same thing as a DNS server on the net? Converts a naming convention to ip?

Webmaster

Yes, and vice versa. But do keep in mind that Microsoft has its own implementation (as always) of DNS. Meaning it offers many proprietary options. An important difference is that Win2000 DNS is dynamic, you can configure your DHCP server to register the IP addresses it issues and their host names to the DNS.

Also the SRV record type plays an important role.... but, if you want more detailed info about DNS:

www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/tcpip/part2/tcpch05.asp

DHCP:

www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/tcpip/part2/tcpch04.asp

pandimus

To sum it up:

DNS provides name resolution by mapping host names to IP addresses and vice versa.

skardos

I have to throw in my two cents worth.

Remember that when the Active Directory is created you create a 'domain' like "mycompany.com". All computers within the domain have an address like "mylaptop.mycompany.com". In order to have the abilty to access shared resources in the Active Directory domain these names must be resolved to their IP addresses.

The reason behind authorizing DNS in Active Directory is that no 'rogue' DNS servers can be introduced and having their (rogue) DNS databases replicated to other 'authorized' DNS servers in the Enterprise. Esentially avoiding unauthorized computers to be added to the network.

SK

Lexxdymondz

I don't mean to be picky but I've never authorized a DNS server before.

You need to authorize a DHCP server so no "rogue" DCHP servers can give out address leases.

skardos

Sorry for the delay in replying but I don't get out as much as used to. Working two jobs a little too much at times.

DNS gets automatically authorized when you install it. Also when you 'introduce' a new server, which has a DNS server on it you need to supply the Administrator's Password thus 'triggering' the authorization.
Another thing that needs 'authorization' is the Dynamic DNS portion, which should be turned on since this is the best part of DNS in a Win2K+ environment.

S