zones not being added to /etc/bind/named.conf.local

Discussion in 'Installation/Configuration' started by Bret Gordon, Nov 1, 2016.

  1. Bret Gordon

    Bret Gordon New Member

    This is a 1&1 virtual server running Debian 7. From a clean, updated image I've installed 3.1.1p1 using the automated setup script, installed Webmin, and applied some standard security: disabled DNS recursion & root SSH login, and applied ISPConfig firewall using default settings except for closing the mysql UDP port.

    As the title states, when I add a DNS zone in ISPConfig it does not update the DNS configuration. This started when I initially upgraded from 3.1dev to 3.1 stable before I re-imaged.

    I've run the test script and received the following warning: "[WARN] could not determine server's ip address by ifconfig". As this is a VPS, I cannot change the hostname (the test script properly resolved the IP address from the hostname) or the interfaces file. However, it appears that I might be able to do something with /etc/network/interfaces.template if necessary:

    Code:
    # ifconfig
    lo  Link encap:Local Loopback 
      inet addr:127.0.0.1  Mask:255.0.0.0
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING  MTU:65536  Metric:1
      RX packets:58642 errors:0 dropped:0 overruns:0 frame:0
      TX packets:58642 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:5286125 (5.0 MiB)  TX bytes:5286125 (5.0 MiB)
    
    venet0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
      inet addr:127.0.0.1  P-t-P:127.0.0.1  Bcast:0.0.0.0  Mask:255.255.255.255
      UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
      RX packets:165051 errors:0 dropped:0 overruns:0 frame:0
      TX packets:150855 errors:0 dropped:2 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:22918636 (21.8 MiB)  TX bytes:14467904 (13.7 MiB)
    
    venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
      inet addr:***.***.***.***  P-t-P:74.208.167.54  Bcast:***.***.***.***  Mask:255.255.255.255
      UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
    
    Code:
    # cat /etc/network/interfaces
    # This configuration file is auto-generated.
    # WARNING: Do not edit this file, otherwise your changes will be lost.
    # Please edit template /etc/network/interfaces.template instead.
    
    
    auto lo
    iface lo inet loopback
       address 127.0.0.1
       netmask 255.0.0.0
       broadcast 127.255.255.255
       up ip route replace 127.0.0.0/8 dev lo
    
    
    # Auto generated venet0 interfaces
    auto venet0
    iface venet0 inet static
       address 127.0.0.1
       netmask 255.255.255.255
       broadcast 0.0.0.0
    
       up route add default dev venet0
    
    auto venet0:0
    iface venet0:0 inet static
       address ***.***.***.***
       netmask 255.255.255.255
    
    Code:
    # cat /etc/network/interfaces.template
    
    auto lo
    iface lo inet loopback
       address 127.0.0.1
       netmask 255.0.0.0
       broadcast 127.255.255.255
       up ip route replace 127.0.0.0/8 dev lo
    
    Any help would be greatly appreciated as this is a production server for my MSP.
     
    Last edited: Nov 1, 2016
  2. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    Check your dns-zones and for *err-files in /etc/bind
     
  3. Bret Gordon

    Bret Gordon New Member

    yes, .err file exists for the zone & it consists of the correct records. zones file consists of several entries similar to this:
    zone "10.in-addr.arpa" { type master; file "/etc/bind/db.empty"; };
     
  4. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    If you see err-files, something is wrong with your zone-file and the zone will not be added to bind.
     
  5. Bret Gordon

    Bret Gordon New Member

    OK, i will look into that. TYVM :)
     
  6. Bret Gordon

    Bret Gordon New Member

    I downloaded the root servers again, but /etc/resolv.conf keeps going back to 1&1 nameservers after I set it to localhost in Webmin, so I'm assuming that's the problem. I'm attempting resolvconf now and will let you know probably tomorrow. I sincerely hate DNS. :mad:
     
  7. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    Your local resolver has nothing to do with wrong zone-files in your dns.
     
  8. Bret Gordon

    Bret Gordon New Member

    Sorry, I'm confused. Which zone files are you talking about? The only zone files in my DNS are the defaults, and I've re-loaded the root zone as I mentioned previously. Do you mean the ones that I'm trying to create? I've been using the wizard for that the same as I always have, but I just tried adding one manually in ISPConfig and still got the .err file.
     

Share This Page