Where are important name server configuration file stored in FreeBSD 8.3

I have a mail server alongside with name server.
I want to Backup information. What should I save as backup? Related to the bind name server.
Is this directory enough to save
/etc/namedb
?

How to backup information in future?
I have using Communigate and bind name server.
The question is about mechanism of backup information.
Nusrat NuriyevAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

arnoldCommented:
IMHO, best backup deals with having a secondary/slave and then backup the named.conf file.
Look into having mysql backend.

 It takes a few seconds to convert an instance configured as salve into a primary role.

I.e. Named.conf change removing type slave and commenting out the masters{} entry! and reconfiguring/reloading named.
0
gheistCommented:
First file - /etc/named.conf (it might be symlink to 2nd)
Second - directory /var/named except for dynamic and log subdirectories)
0
Nusrat NuriyevAuthor Commented:
Is chroot like "sandbox"?
in case of /usr/local/etc/rc.d  /etc/rc.d pair
what is original?
0
Nusrat NuriyevAuthor Commented:
arnold, could you provide an article/methodology which shows that it's easy to do what you are saying. But in more details. In my settings there are both settings for current zone is type of master.
0
arnoldCommented:
You have two systems.
one master with allow-transfer { ip of slave;} in the options.

on the slave, the named.conf for the zone has
type slave
master {ip of master}

The difference, will be the format of the file.

Now should the master stop functioning.
Replacing the current slave named.conf with the named.conf from the master will convert the former backup server into the master role.

.i.e. replacing type slave; master {ip of master}; with type master;
master zone
zone "somedomain.com" {
type master;
file "db.somedomain.com";
};

slave zone
zone "somedomain.com" {
type slave;
file "db.domedomain.com";
master {ip of master;};
};

dig @127.0.0.1 AXFR somedomain.com.
Usually the configuration includes that localhost is allowed to transfer.

The output is what the secondary file will look like and is a valid format for bind, while not most convinient for human readable.....

After the change on your existing server you would run the reconfigure/reload to get named to reread the configuration file.

rndc reconfig
rndc reload

http://www.experts-exchange.com/OS/Linux/Q_28252748.html

A search for bind master/slave yields a variety of articles.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.