freddes
27/01/2016, 18h21
Je vient de revérifier et, oui, c'était bien le cas
allow-transfer { ...... 213.251.188.141; 2001:41d0:1:4a8d::1;
listen-on-v6 { none; };
// This is the primary configuration file for the BIND DNS server named. // // Please read /usr/share/doc/bind9/README.Debian.gz for information on the // structure of BIND configuration files in Debian, *BEFORE* you customize // this configuration file. // // If you are just adding zones, please do that in /etc/bind/named.conf.local include "/etc/bind/named.conf.options"; include "/etc/bind/named.conf.local"; include "/etc/bind/named.conf.default-zones"; key rndc-key { algorithm hmac-md5; secret "sssssssssssssssssssssss=="; }; controls { inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { rndc-key; }; };
options { directory "/var/cache/bind"; // If there is a firewall between you and nameservers you want // to talk to, you may need to fix the firewall to allow multiple // ports to talk. See http://www.kb.cert.org/vuls/id/800113 // If your ISP provided one or more IP addresses for stable // nameservers, you probably want to use them as forwarders. // Uncomment the following block, and insert the addresses replacing // the all-0's placeholder. // forwarders { // 0.0.0.0; // }; //======================================================================== // If BIND logs error messages about the root key being expired, // you will need to update your keys. See https://www.isc.org/bind-keys //======================================================================== dnssec-validation auto; auth-nxdomain no; # conform to RFC1035 listen-on-v6 { none; }; listen-on { any; }; };
// // Do any local configuration here // // Consider adding the 1918 zones here, if they are not used in your // organization //include "/etc/bind/zones.rfc1918"; zone "8sur7.com" { type master; file "/var/lib/bind/8sur7.com.hosts"; allow-transfer { 127.0.0.1; localnets; 213.251.188.141; 2001:41d0:1:4a8d::1; }; };
named.conf.option: options { directory "/var/cache/bind"; // If there is a firewall between you and nameservers you want // to talk to, you may need to fix the firewall to allow multiple // ports to talk. See http://www.kb.cert.org/vuls/id/800113 // If your ISP provided one or more IP addresses for stable // nameservers, you probably want to use them as forwarders. // Uncomment the following block, and insert the addresses replacing // the all-0's placeholder. // forwarders { // 0.0.0.0; // }; //======================================================================== // If BIND logs error messages about the root key being expired, // you will need to update your keys. See https://www.isc.org/bind-keys //======================================================================== dnssec-validation auto; auth-nxdomain no; # conform to RFC1035 listen-on-v6 { none; }; listen-on { any; }; };
zone "8sur7.com" { type master; file "/var/lib/bind/8sur7.com.hosts"; allow-transfer { 127.0.0.1; localnets; 213.251.188.141; 2001:41d0:1:4a8d::1; }; };
Jan 26 07:49:23 vps239540 named[24677]: zone 8sur7.com/IN: sending notifies (serial 2016012500)
;; ANSWER SECTION: 8sur7.com. 38400 IN SOA ns3369728.ovh.net. root.ns3369728.ovh.net. 2016010802 10800 3600 604800 38400 8sur7.com. 38400 IN A 37.187.91.63 8sur7.com. 38400 IN NS ns3369728.ovh.net. 8sur7.com. 38400 IN NS sdns2.ovh.net. 8sur7.com. 38400 IN AAAA 2001:41d0:a:333f::1 8sur7.com. 38400 IN TXT "v=spf1 a mx a:8sur7.com ip4:37.187.91.63 ip6:2001:41D0:A:333f::1 ?all" 8sur7.com. 38400 IN MX 5 mail.8sur7.com.