Navigation

arnaud · #11 31st January 2007, 15:42

Debian sarge set this at install time in named.conf :
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
notice that zone "localhost" => file db.local
and zone "127.in-addr.arpa" => file db.127
ISPConfig set this in named.conf after configuring some dns zone :
zone "0.0.127.in-addr.arpa" {
type master;
file "db.local";
};
notice it's a mix between the "127.in-addr.arpa" zone et the "localhost" zone, and when I perform zonecheck test which is very strict regarding rfc, it issue an error.
But everything is working but it break rfc according to zonecheck.

arnaud · #12 2nd March 2007, 16:47

Hello,

I found that I can make changes in /root/ispconfig/isp/conf/named.conf.master
(I don't know if it stays after ISPConfig's update).

For my configuration (I've another dns server which is master for reverse zone), I've made this change :
delete

Code:

zone "0.0.127.in-addr.arpa" {
         type master;
         file "db.local";
};

and for not to be master for reverse, delete

Code:

<!-- BEGIN DYNAMIC BLOCK: named_reverse -->
zone "{ZONE}.in-addr.arpa" {
        type master;
        file "pri.{ZONE}.in-addr.arpa";
};
<!-- END DYNAMIC BLOCK: named_reverse -->

and I've add this at end of /etc/bind/named.conf (for Debian sarge)

Code:

//// MAKE MANUAL ENTRIES BELOW THIS LINE! ////
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
        type master;
        file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
        type master;
        file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
        type master;
        file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
        type master;
        file "/etc/bind/db.255";
};
// fin RFC 1912

It works !