DNS server setup

[Christopher M Downs]

the purpose of having 2 dns servers is so that replication and dns 
failover is available for your records. You should want the primary dns 
server on a reliable connection and the second could be on a cable 
network if need be.

Remember anything updated on the master will be pushed to the slave. You 
must always remember to update your serial num on the master when 
rehupping the service, this is what tells bind "oh hey we have new 
records, lets find all corrisponding slaves and 'notify' them"

here is a power dns chroot $ENV I  wrote for use under redhat, chrooting 
bind is a highly recommended proceedure.

http://www.lifeatzero.com/howto/chroot_named.txt

if this was an internal dns server I would recommend using named ACL 
lists for network request verification.

hope this helps.

~!>D

Matthew Freeland wrote:

>Hi.  I own the domain mfreeland.net, which I wish to use as my personal domain 
>for email/web site/ftp/telnet/etc.  I read a HOWTO for BIND9 and set up the 
>server.  All seems to be working when I dig to localhost, so I think I have 
>everything configured.  If you need it, I can send coppies of my named.conf 
>and zone files.  The problem I have is that when I went to my registrar, 
>godaddy.com, and tried to change my nameservers to ns.mfreeland.net (my 
>machine), it said a) you need 2 nameservers, and b) the nameserver is not 
>registered.  What must I do to get the nameserver registered, and is there 
>any way to get around needing 2 nameservers?  My server will be running from 
>my dorm room, so I don't think they'll want me running 2 PCs fulltime.  I 
>understand that the slave server is supposed to be there in case the primary 
>fails, but honestly, I don't care if my website goes down for a short time; 
>it's just a private website.  Thanks in advance for any help.
>
>
>Matthew Freeland
>
>PS   Sorry if this goes out twice, I'm having trouble with the emtp server 
>that my address is currently routed to.
>
>
>
>
>  
>