Bind - Historique des versions

193.252.149.222 le 9 juin 2010 à 13:02

2010-06-09T13:02:01Z

← Version précédente		Version du 9 juin 2010 à 13:02
Ligne 2 :		Ligne 2 :
	options {		options {
	directory "/var/bind";		directory "/var/bind";

	// uncomment the following lines to turn on DNS forwarding,		// uncomment the following lines to turn on DNS forwarding,
	// and change the forwarding ip address(es) :		// and change the forwarding ip address(es) :
Ligne 10 :		Ligne 10 :
	// 123.123.123.123;		// 123.123.123.123;
	//};		//};

	listen-on-v6 { any; };		listen-on-v6 { any; };
	// listen-on { 127.0.0.1; };		// listen-on { 127.0.0.1; };

	// to allow only specific hosts to use the DNS server:		// to allow only specific hosts to use the DNS server:
	//allow-query {		//allow-query {

193.252.149.222 le 9 juin 2010 à 13:01

2010-06-09T13:01:38Z

← Version précédente		Version du 9 juin 2010 à 13:01
Ligne 18 :		Ligne 18 :
	// 127.0.0.1;		// 127.0.0.1;
	//};		//};

	// if you have problems and are behind a firewall:		// if you have problems and are behind a firewall:
	//query-source address * port 53;		//query-source address * port 53;

	pid-file "/var/run/named/named.pid";		pid-file "/var/run/named/named.pid";

	listen-on { 87.98.150.11; 127.0.0.1; };		listen-on { 87.98.150.11; 127.0.0.1; };

	allow-query { 127.0.0.1; ::1; };		allow-query { 127.0.0.1; ::1; };

	allow-recursion { 127.0.0.1; };		allow-recursion { 127.0.0.1; };

	//forwarders { 213.251.188.140; 91.121.192.46;};		//forwarders { 213.251.188.140; 91.121.192.46;};

	also-notify { 213.251.188.140; 91.121.192.46;};		also-notify { 213.251.188.140; 91.121.192.46;};

	allow-transfer { 213.251.188.140; 91.121.192.46;};		allow-transfer { 213.251.188.140; 91.121.192.46;};
	};		};

193.252.149.222 le 9 juin 2010 à 13:01

2010-06-09T13:01:18Z

Nouvelle page

ns357151 ~ # cat /etc/bind/named.conf
options {
directory "/var/bind";

// uncomment the following lines to turn on DNS forwarding,
// and change the forwarding ip address(es) :
//forward first;
//forwarders {
// 123.123.123.123;
// 123.123.123.123;
//};

listen-on-v6 { any; };
// listen-on { 127.0.0.1; };

// to allow only specific hosts to use the DNS server:
//allow-query {
// 127.0.0.1;
//};

// if you have problems and are behind a firewall:
//query-source address * port 53;

pid-file "/var/run/named/named.pid";

listen-on { 87.98.150.11; 127.0.0.1; };

allow-query { 127.0.0.1; ::1; };

allow-recursion { 127.0.0.1; };

//forwarders { 213.251.188.140; 91.121.192.46;};

also-notify { 213.251.188.140; 91.121.192.46;};

allow-transfer { 213.251.188.140; 91.121.192.46;};
};

// Briefly, a zone which has been declared delegation-only will be effectively
// limited to containing NS RRs for subdomains, but no actual data beyond its
// own apex (for example, its SOA RR and apex NS RRset). This can be used to
// filter out "wildcard" or "synthesized" data from NAT boxes or from
// authoritative name servers whose undelegated (in-zone) data is of no
// interest.
// See http://www.isc.org/products/BIND/delegation-only.html for more info
//zone "COM" { type delegation-only; };
//zone "NET" { type delegation-only; };

zone "." IN {
type hint;
file "named.ca";
};
zone "localhost" IN {
type master;
file "pri/localhost.zone";
allow-update { none; };
notify no;
};
zone "127.in-addr.arpa" IN {
type master;
file "pri/127.zone";
allow-update { none; };
notify no;
};
zone "audenge-beta.fr" {
type master;
file "/var/bind/audenge-beta.fr.hosts";
allow-query { any; };
};