DNS for secondary nameserver

DNS for secondary nameserver, Bind/named.config (1 Replies, Read 138043 times)

hank22077	# August 23, 2022, 9:44 pm
Group: Member Post Group: Newbie Posts: 4 Status:	Hello, Can anyone give me advice on how to set up my named.config to push zones to a secondary nameserver? I have this: options { /* make named use port 53 for the source of all queries, to allow * firewalls to block all ports except 53: / // query-source port 53; / We no longer enable this by default as the dns posion exploit has forced many providers to open up their firewalls a bit / // Put files that named is allowed to write in the data/ directory: directory "/var/named"; // the default pid-file "/var/run/named/named.pid"; dump-file "data/cache_dump.db"; statistics-file "data/named_stats.txt"; / memstatistics-file "data/named_mem_stats.txt"; / allow-transfer {"none";}; }; logging { / If you want to enable debugging, eg. using the 'rndc trace' command, * named will try to write the 'named.run' file in the $directory (/var/named"). * By default, SELinux policy does not allow named to modify the /var/named" directory, * so put the default debug log file in data/ : / channel default_debug { file "data/named.run"; severity dynamic; }; }; zone "." IN { type hint; file "/var/named/named.ca"; }; / these are zones that contain definitions for all the localhost * names and addresses, as recommended in RFC1912 - these names should * ONLY be served to localhost clients: */ include "/var/named/named.rfc1912.zones"; It's the default named.config. I add my second IP in the allow-transfer, but it doesn't save. It keeps resetting to none. I'd really like to use Webuzo, but I really need to be able to push zones to a secondary nameserver Thanks for any help and advice
IP: --

Users viewing this topic
	1 guests, 0 users.