How to make named.conf.options persistent

Discussion in 'Server Operation' started by FredZ, Nov 18, 2024.

  1. FredZ

    FredZ Member HowtoForge Supporter

    Hello
    I am wanting to set some options within bind (named.conf.options) and I am wanting to know how to make them persistent as ISPConfig seems to over write it.

    (Debian Bookworm) ISPConfig 3.2.12p1
    This is a new install using the autoinstall script.

    Regards

    Fred
     
  2. remkoh

    remkoh Active Member HowtoForge Supporter

    Never had any problem of it being overwritten.
    Only named.conf.local
     
  3. FredZ

    FredZ Member HowtoForge Supporter

    You are correct, the named.conf.local files does get over written. And that was the file I referred to.
    So how/where do I declare options so they become persistent?
    Regards

    Fred
     
  4. remkoh

    remkoh Active Member HowtoForge Supporter

    Put it in named.conf.options
     
  5. FredZ

    FredZ Member HowtoForge Supporter

    Your NOT reading my posts properly.
    named.conf.options is being over written, therefore any options manually put into that file are NOT persistent.

    So I repeat my question. How/where do I put options so they become persistent?

    Regards

    Fred
     
  6. remkoh

    remkoh Active Member HowtoForge Supporter

    named.conf.options should not get to be overwritten by ISPC, only named.conf.local is rewritten when adding or deleting a domain.
    The file name explains its use, for options. Including your desired custom ones.
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    I guess named.conf.options might get overwritten on ISPConfig update. In that caye, copy the template file of the config file that gets overwritten from ISPConfig tar.gz (see install/tpl/ folder in the tar.gz file) to the folder /usr/local/ispconfig/server/conf-custom/install/ and modify it there.
     
    Dmitriy, ahrasis and remkoh like this.
  8. remkoh

    remkoh Active Member HowtoForge Supporter

    Interesting, hadn't thought of that scenario.
    (Also wasn't made clear when it got overwritten)
     
  9. FredZ

    FredZ Member HowtoForge Supporter

    Thank you for the suggestion Till. That worked a treat.

    Regards

    Fred
     
    till likes this.
  10. dan-v

    dan-v Member

    Hello Till,

    I tried that method to implement a permanent change to /etc/dovecot/dovecot-sql.conf :

    I retrieved from https://git.ispconfig.org/ispconfig/ispconfig3/-/tree/develop/install/tpl a file named debian_dovecot-sql.conf.master, which I renamed dovecot-sql.conf.master and, after editing it, I placed it in /usr/local/ispconfig/server/conf-custom/install/ as you suggested.

    Although update_ISPConfig.sh does flag it as a master and offers to rename it in order to suppress its effect, it then seems to ignore it after the rename has been refused: the changes in the master are not reflected in the re-installed /etc/dovecot/dovecot-sql.conf.

    What am I doing wrong ?
     
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    You went wrong at that point; do not rename the master config file.
     
  12. dan-v

    dan-v Member

    Thanks Till.

    I just retried with the original name. It still does not work :(
     
  13. till

    till Super Moderator Staff Member ISPConfig Developer

  14. dan-v

    dan-v Member

    Thank you very much, Till
    It worked perfectly
     

Share This Page