meesed up default service confgi files ? all directadmin default build configuration

[rnc]

hello
to days i messed up my named.conf file when i ran a wrong sed -i command
so i searched google to find how and where to find rebuild this file or find default file content
i reached this page
https://kb.hivelocity.net/how-do-i-rebuildrestore-the-named-conf-file-on-a-direct-admin-server-2/
in this page writer referred to a named.conf file on directadmin servers

http://www.directadmin.com/named.conf

i want to know is this file is up2date and latest version that directadmin use?

because i saw the default directadmin named.conf file is default redhat binaries file
but this files is different
and for each of this
you need to use this tread to add named DB's to named.conf file
http://help.directadmin.com/item.php?id=393

if these files are update and latest version where can i find list of theses files ?
if there is no list please post theme in this topic so i collect them and make this topic as a reference

 

[nobaloney]

It's a start, but it's inconsistent. For example, the comments say it's for use as a caching nameserver, but you'll be adding lines and using it as an authoritative nameserver.

I hope that John will answer and perhaps update the file. I have my own file I've been using (changing from time to time) which I can offer to the community, depending on John's reply to this thread.

Jeff

 

[DirectAdmin Support]

The named.conf files vary quite a bit from OS to OS, even between releases of the OS.
So there is not going to be any single answer for your question.
We rely on the bind packages including their own correctly setup named.conf, plus some install changes by DA.
The above file is really only as a last resort.

For CentOS 6 64-bit.. here's what we currently have (this is after the DA install, which does changes some lines via the doChecks.sh script):

//// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//


options {
        //listen-on port 53 { 127.0.0.1; };
        //listen-on-v6 port 53 { ::1; };
        directory       "/var/named";
        dump-file       "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";
        allow-query     { any; };
        allow-transfer  { none; };
        allow-recursion { localhost; };
        recursion yes;


        dnssec-enable yes;
        dnssec-validation yes;
        dnssec-lookaside auto;


        /* Path to ISC DLV key */
        bindkeys-file "/etc/named.iscdlv.key";


        managed-keys-directory "/var/named/dynamic";
};


logging {
        channel default_debug {
                file "data/named.run";
                severity dynamic;
        };
};


zone "." IN {
        type hint;
        file "named.ca";
};


include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";

and then you'd have all of your zones below that.

John