none

 
UI's: X, Web, Command, API
Download Full Demo Now
Reduce Operations Costs
Technical Information
Staging / Failover
IP Management
Snapshots
Solaris 10!
README
Converter
Buy Online
Documentation
BIND: 4.x, 8.x, 9.x
Open And Extensible
Platforms: Solaris, Linux
Other resources
Backup Power Generators
 

none

DNS file generators for UNIX. With the DNS Boss file generators, you can easily create your ASCII DNS BIND files for your DNS servers. No need to do it by hand.
none none none none





How do I set up a DNS secondary?

     After you have saved the DNS configurations for 
your DNS domain (the DNS primary), go to the machine 
that you wish to use as a secondary, either by telnet
on a UNIX machine, or by walking up to it in person 
on a non-UNIX machine.  You may create the DNS 
secondary by using the DNS Boss GUI, or by doing the 
eqivalent of these commands from the command line:

mkdir -p /var/opt/DNSBoss/dns_secondary

cd /var/opt/DNSBoss/dns_secondary

ftp name_of_dns_primary_that_has_dnsboss_installed
ftp> cd /var/opt/DNSBoss/dns_build_area

ftp> dir
yourcompany.com

ftp> cd yourcompany.com  
ftp> dir
ftp> get named.boot_for_secondary
ftp> get named.conf_for_secondary
ftp> get db.cache
ftp> get db.127.0.0
ftp> quit

On a SUN, or HPUX machine:
     For Solaris 2.5 and Solaris 2.6 ( Bind 4.x )
          mv named.boot_for_secondary /etc/named.boot
     For Solaris 2.7 or greater ( BIND 8.x, or 9.x )
          mv named.conf_for_secondary /etc/named.conf
     
     For Solaris
          vi /etc/nsswitch.conf
          Make sure the following exists:
          hosts:      files dns
          Save the file.

     reboot

On an SGI 
     chkconfig named on
     uname -r
     If it is 4.X.X.
        mv named.boot_for_secondary 
           /usr/etc/named.d/named.boot
     Otherwise,
        mv named.boot_for_secondary /etc/named.boot
     reboot

     Thats it, you should be done.  The secondary's 
should pull over the latest DNS databases after you
make changes to them.  You do not need to add a 
/etc/resolv.conf on a UNIX machine that is acting as
a DNS primary or secondary.  It automatically know 
how to resolve IP addresses as long as it is 
functioning properly.
     Make sure you test everything.  The nslookup 
command is a great way to do this.  On most Unix 
machines you can type:
nslookup - yoursecondary.yourcompany.com.
> ls -t any yourcompany.com.
This should give you a good idea if you are on track.