Sometimes, named.conf lost first lines of file.

speckados

Well-Known Member
hello

There're any issue on powerdns on my servers.

Since yesterday, /etc/named.conf loss first lines of file
## Lost this lines
Code:
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;

recursion no;

/* 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 {
channel default_log {
file "/var/log/named/named.log" versions 5 size 128M;
print-time yes;
print-severity yes;
print-category yes;
severity warning;
};
category default { default_log; };
category general { default_log; };
};

// All BIND 9 zones are in a "view", which allow different zones to be served
// to different types of client addresses, and for options to be set for groups
// of zones.
//
// By default, if named.conf contains no "view" clauses, all zones are in the
// "default" view, which matches all clients.
//
// If named.conf contains any "view" clause, then all zones MUST be in a view;
// so it is recommended to start off using views to avoid having to restructure
// your configuration files in the future.

view "localhost_resolver" {
/* This view sets up named to be a localhost resolver ( caching only nameserver ).
* If all you want is a caching-only nameserver, then you need only define this view:
*/
match-clients { 127.0.0.0/24; };
match-destinations { localhost; };
recursion yes;

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";
};

view "internal" {
/* This view will contain zones you want to serve only to "internal" clients
that connect via your directly attached LAN interfaces - "localnets" .
*/
match-clients { localnets; };
match-destinations { localnets; };
recursion yes;

zone "." IN {
type hint;
file "/var/named/named.ca";
};

// include "/var/named/named.rfc1912.zones";
// you should not serve your rfc1912 names to non-localhost clients.

// These are your "authoritative" internal zones, and would probably
// also be included in the "localhost_resolver" view above :
I've two nameserver in cluster for all my network using cpanel-dnsonly
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
11,032
1,741
363
cPanel Access Level
Root Administrator
Hey hey! Are you saying all the lines in the code block are missing from all servers with PowerDNS? I just checked a PowerDNS machine that is live and serving zones and I don't see that missing on my end, and I don't see any recent changes to PowerDNS in the update logs on that machine.

If you run "/scripts/rebuilddnsconfig" do those lines get added back to named.conf?
 

speckados

Well-Known Member
Solution for me is:
- Get alerta of my zabbix monitoring that problems with resolver
- Go to one of cPanelDNSOnly server and run /usr/local/cpanel/scripts/rebuilddnsconfig and this scripts rewrite perfectly zone and sync to another server.

But that is porcess for repair.

I am looking for cause of error.
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
11,032
1,741
363
cPanel Access Level
Root Administrator