Two identical servers, different named.conf Logging section

[Metro2]

I couldn't decide whether this post should be here in the DNS forum or in the CloudLinux forum since the OS is CL 6.7 , but since the question is in regard to named.conf I decided to post here in DNS forum.

I recently purchase two brand new identical servers - same hardware, same versions of all software (same OS, cPanel, WHM, CSF, PHP, Apache, etc...) but the Logging section of /etc/named.conf is different from one to the other.

I'm hoping that someone here can tell me which version of the named.conf Logging section appears to be the correct one.

On SERVER 1 the /etc/named.conf Logging section looks like this:

logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};

One SERVER 2 the /etc/named.conf Logging section looks like this:

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


Can anyone here tell me which version appears to be the correct one?

Thank you for any feedback!

 

[cPanelMichael]

Hello

Here's the entry on a test machine running CentOS 7.2:

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

Check to see the output of the following command on each server:

rpm -qa|grep bind

Also, you can run the following commands to rebuild the /etc/named.conf file to it's default state:

mv /etc/named.conf /etc/named.conf.backup1
/scripts/rebuilddnsconfig

Thank you.

 

[Metro2]

Check to see the output of the following command on each server:

rpm -qa|grep bind

Hi cPanelMichael, thanks for chiming-in.

After running that command on each new box, it appears there are some things that aren't as identical on these "twin" servers as I thought.

SERVER 1 Returns:

[~]# rpm -qa|grep bind
bind-devel-9.8.2-0.37.rc1.el6_7.6.x86_64
rpcbind-0.2.0-11.el6.x86_64
bind-libs-9.8.2-0.37.rc1.el6_7.6.x86_64
bind-9.8.2-0.37.rc1.el6_7.6.x86_64
samba-winbind-clients-3.6.23-24.el6_7.x86_64
bind-utils-9.8.2-0.37.rc1.el6_7.6.x86_64
samba-winbind-3.6.23-24.el6_7.x86_64
ypbind-1.20.4-31.el6.x86_64
cpanel-bindp-1.0.0-1.cp1152.x86_64

SERVER 2 Returns:

[~]# rpm -qa|grep bind
cpanel-bindp-1.0.0-1.cp1152.x86_64
bind-libs-9.8.2-0.37.rc1.el6_7.6.x86_64
bind-devel-9.8.2-0.37.rc1.el6_7.6.x86_64
bind-9.8.2-0.37.rc1.el6_7.6.x86_64
bind-utils-9.8.2-0.37.rc1.el6_7.6.x86_64

Clearly there are a few extra bind modules on the first server. But I'm not sure why. I was recently provisioned both servers from the same company in the same data center, both orders placed identically. Both boxes are CloudLinux 6.7 and cPanel 54 (release tier).

I'm a tad hesitant to run the named rebuild because both servers are in production now and I'm not sure what exactly this difference above imply.

Thanks for your response and valuable time as always. You're an incredible help on here!

 

[cPanelMichael]

I'm a tad hesitant to run the named rebuild because both servers are in production now and I'm not sure what exactly this difference above imply.

The command simply rebuilds the /etc/named.conf file. You can back this file up before running "/scripts/rebuilddnsconfig" so you can restore it should it result in any issues.

Thank you.

 

[Metro2]

Thanks very much for your input cPanelMichael.

After running /scripts/rebuilddnsconfig it seems that the default for both CloudLinux 6.7 boxes wants to be:

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

It's comforting to have some consistency there.

I still have no idea why the extra rpcbind and ybind packages are installed on Server 1 but not Server 2 when I run "rpm -qa|grep bind" since both servers were supposed to be identically provisioned to be "twins" from the same provider / same data center, but from everything I've read those appear to be harmless so I'm not about to touch them

 

[cPanelMichael]

I still have no idea why the extra rpcbind and ybind packages are installed on Server 1 but not Server 2 when I run "rpm -qa|grep bind" since both servers were supposed to be identically provisioned to be "twins" from the same provider / same data center

You may want to contact your provider or data center to determine how their images are configured.

Thank you.