Configure Public & Private DNS Server

I need to configure 2 DNS server in my network. 1 will handle the
public addresses and one for the company's network. Can someone direct
me to the right place to find articles on the proper way of doing that?

In article <(E-Mail Removed) .com>,
No_Spam wrote:

>I need to configure 2 DNS server in my network. 1 will handle the
>public addresses and one for the company's network. Can someone direct
>me to the right place to find articles on the proper way of doing that?

Not quite clear - is that one outside for the world to see, and one
inside for your company use only?

The official servers (those listed in your domain registration) are best
living in the DMZ and/or some off-site location, such that a single outage
of power or networking or hot buttered rum doesn't prevent external queries
from being answered. This is particularly important if you have multiple
MX servers in more than one location.

Your internal servers should be behind the corporate firewall, and if you
are smart enough to not be allowing access from the world to your internal
hosts, this/these internal servers should be firewalled to prevent them
responding to public queries for private addresses. These same internal
servers can be set to act as a regular name server (able to recursively
resolve external addresses) or as a caching/forwarding nameserver so that
your internal hosts can resolve external names as needed.

The DNS-HOWTO is a bit dated, but should set you in the right direction.
A better document is the 'cricket book' ("DNS and BIND, 4th Edition" Apr
2001, 622 pgs, O'Reilly & Assoc., ISBN 0-596-00158-4, US$45) and the
companion "DNS & BIND Cookbook" Oct 2002, 240 pgs, O'Reilly & Assoc., ISBN
0-596-00410-9, US$35. The HOWTO should be with all Linux distributions,
or on the web at http://ibiblio.org/pub/linux/docs/HOWTO/ or
http://en.tldp.org/HOWTO/HOWTO-INDEX/howtos.html

-rw-rw-r-- 1 gferg ldp 91563 Dec 23 2001 DNS-HOWTO

One really really important thing you have to remember about DNS is that
the resolver (no matter what the O/S) believes the first answer that it
receives - even if that answer is "I don't know". If it gets that answer,
the resolver is done - it will NOT go trying another nameserver. Thus,
any name server you have must be able to give the "correct" answer.

Old guy