DNS improvements

Discussion in 'Feature Requests' started by fireba11, Apr 2, 2010.

  1. fireba11

    fireba11 New Member

    * add spf record to the default template
    * add "Allow zone transfers to these IPs" as option for the template

    spf records (when set correctly) are always a good idea to have ..
    currently the template does not allow predefining IPs for AXFR, usually you always use the same secondary DNS servers though, so that would be nice to have in the template
     
  2. tried both versions and I couldn't get either to work.

    I couldn't get them to hold the configuration settings. After saving the router settings the router went back to the default.

    Maybe its something I'm doing wrong. If some else gets them to work I'll have another try?
     
  3. coldfried

    coldfried New Member

    Dynamic DNS

    * native support for zone options such as "update-policy" and "allow-update" in /etc/bind/named.conf.local for the zone.
    * native support to store a secret in /etc/bind/named.conf.keys (my config) for the dynamic zones.

    I am running a dynamic dns zone on my name server controlled by ISPconfig3, and I've just discovered that when I make any changes to the name server within ISPconfig afterwards, it rewrites the conf file for the zone and removes my modifications that permit dynamic updates. It would be great if these dynamic update settings could be supported by (or included in) ISPConfig 3 so that we would not need to devise a workaround to get it to keep the changes. :)
     
  4. till

    till Super Moderator

    ISPConfig supports already custom BIND config files.

    To make your changes persistent, copy the bind_* files from /usr/local/ispconfig/server/conf to /usr/local/ispconfig/server/conf-custom/ and then edit the files in the conf-custom directory to suit your needs.
     
  5. DiscipleGeek

    DiscipleGeek New Member

    These would definitely be welcome additions.
     
  6. maumar

    maumar HowtoForge Supporter

    I would add this to this problematic

    Code:
    allow-transfer {none;};
    
    there 2 requirements about it>
    1.

    as fireba11 asked for, add "Allow zone transfers to these IPs" as option for the template (I was not able to customize it working on

    Code:
    /usr/local/ispconfig/server/conf/bind_named.conf.local.master
    
    2.
    there at the moment 3 fields
    -> Allow zone transfers to these IPs (comma separated list)
    -> Also Notify
    -> Update ACL

    if you let empty 2^ one and 3^ one, "Also Notify" and "Update ACL", nothing is written to

    Code:
    zone "zonename" {
            type master;
            allow-transfer {none;};
            file "/etc/bind/pri.zonename";
    };
    
    but if u left empty the 1^ filed:

    "Allow zone transfers to these IPs (comma separated list)"

    you get
    Code:
    allow-transfer {none;};
    
    I expect "none" there if and only if i input "none into the form field, and i expect no line regarding allow-transfer if i left field empty

    in this way, i could configure my preferred
    allow-transfer
    ip's into general file:

    Code:
    /etc/bind/named.conf.options
    
    without losing this setting with

    Code:
    allow-transfer {none;};
    
     

Share This Page