Clarification Required on Location of BIND Zone Files

Discussion in 'Server Operation' started by jonwatson, Aug 11, 2008.

  1. jonwatson

    jonwatson New Member

    Hi All,

    I'm confused over the relationship between some ISPConfig settings and the chrooted BIND daemon.

    In ISPConfig Management -> Settings -> DNS, my Zonefiles dir is set to:

    Code:
    /home/admispconfig/ispconfig/web/multidoc/edit 
    and that location does indeed contain zone files. However, the named.conf file in both /etc and /var/named/chroot/etc has the following directive:

    Code:
    directory "/var/named/chroot/var/named/";
    It seems that ISPConfig is writing the zone files to the /home/admispconfig/ispconfig/web/multidoc/edit location which is consistent with the Zonefiles setting in the DNS settings.

    However, when I attempt to start BIND, it fails because the /home/admispconfig/ispconfig/web/multidoc/edit is outside the chroot:

    Code:
    Starting named: 
    Error in named configuration:
    /etc/named.conf:3: change directory to '/home/admispconfig/ispconfig/web/multidoc/edit' failed: file not found
    
    /etc/named.conf:3: parsing failed
    If I change the Zonefile value in Management -> Settings -> DNS to /var/named/chroot/var/named neither named.conf file is updated with that directive.

    To complicate matters, I am unable to change the Zonefiles Dir directive within ISPConfig. If I attempt to change it from anything other than /home/admispconfig/ispconfig/web/multidoc/edit, it sets it to /etc/bind which is again incorrect. I have to manually change the directory line in the named.conf file to /var/named/chroot/var/named in order for named to start.

    The problem with this is that /var/named/chroot/var/named is not where ISPConfig is writing its zone files. It is writing them to /home/admispconfig/ispconfig/web/multidoc/edit so every time I make a DNS change, I have to manually copy the modified file from /home/admispconfig/ispconfig/web/multidoc/edit to /var/named/chroot/var/named in order for it to take effect.

    Clearly. this setup is borked. Can someone clarify for me what is going on?

    Thanks

    Jon
     
  2. jonwatson

    jonwatson New Member

    Any ideas, anyone? I hate to be pushy, but this is causing BIND to tank on my production servers every time ISPConfig rewrites named.conf and tries to restart named.

    The fact that I can't change the location of the zone files within the ISPCOnfig GUI has to be a bug, no?
     
  3. falko

    falko Super Moderator ISPConfig Developer

  4. jonwatson

    jonwatson New Member

    That sounds like it, thanks!

    I searched exhaustively, but apparently didn't manage to find the right combination.
     

Share This Page