From 6bda80b11fede03e7e255f552d6598bb7910fe5f Mon Sep 17 00:00:00 2001 From: Natanael Copa Date: Tue, 13 Mar 2012 10:36:52 +0000 Subject: main/bind: upgrade to 9.9.0 --- testing/bind/bind.conf | 53 -------------------------------------------------- 1 file changed, 53 deletions(-) delete mode 100644 testing/bind/bind.conf (limited to 'testing/bind/bind.conf') diff --git a/testing/bind/bind.conf b/testing/bind/bind.conf deleted file mode 100644 index d58c61bde..000000000 --- a/testing/bind/bind.conf +++ /dev/null @@ -1,53 +0,0 @@ -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 { none; }; - 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"; -}; - -// 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; -}; -- cgit v1.2.3