Question named / bind - max-cache-size

[Alban Staehli]

Server operating system version

CentOS 7.9

Plesk version and microupdate number

18.0.58 Update #2

Hi,

Attempting to limit memory usage fo Bind on a Plesk / Centos box.
I've read about the max-cache-size option.
I've then created a /etc/named-user-options.conf with following content:
max-cache-size 32m;

Nevertheless, doesn't appear to do anything, after restart and running for about 10min, the bind/named process already uses about 140m of memory, way more than the max-cach-size limit.

Would you know what I did wrong? as this parameter seems to have effect.
Thanks.

 

[Alban Staehli]

this is looking at Bind 9.11 / BIND 9.11.0 Options

 

[Alban Staehli]

Hi again,

I actually realized that the file /etc/named-user-options.conf is not taken into consideration. I did put wrong values in that file on purpose, and named chroot service still started without problem.

Any other way to add options to Bind config?

// -- THE FOLLOWING LINES WERE GENERATED BY PLESK. IF YOU MODIFY THEM, THEY WILL BE OVERWRITTEN WHEN THESE SETTINGS ARE MANAGED IN PLESK UI. --
options {
        include "/etc/named-user-options.conf";

Thank you.

 

[Alban Staehli]

Also attempted the server wide settings for bind in Plesk UI, doesn't work > any parameter being put there isn't being brought into the /etc/named.conf file.

DNS Settings

Plesk comes with a DNS server out of the box and allows both customers and the server administrator to manage a wide range of DNS settings.

docs.plesk.com

 

[Alban Staehli]

Realised that the DNS settings from Plesk UI are going into /var/named/chroot/etc/named-user-options.conf and are actually being taken into account.
In brief, anything in /etc/ for named/Bind shall be ignored.

 

[Alban Staehli]

Ended having it working by doing so, since the checkconf was running against proper chrooted file, but execution of service still based on /etc:

ln -s /var/named/chroot/etc/named-user-options.conf /etc/named-user-options.conf