DNS questions

Discussion in 'Installation/Configuration' started by FredZ, Aug 14, 2019.

  1. FredZ

    FredZ Member HowtoForge Supporter

    Hello all

    I must also appologise in advance if I am using the incorect terminology.

    I am attempting to setup DNS on my server.
    When I open the DNS Zone Wizard I see that DKIM si greyed out with a tick in the box. I have no way to turn this on/off.

    All zones are there when I view them in the DNS zone panel.

    I then check the zone file on the server and it has a .err extension (pri.corpcomp.co.nz.err) which I can't help but feel is wrong.

    using dig @serverip all corpcomp.co.nz does not show the zones as created using the default template. Maybe this only works once I have pointed my name servers at my server.

    I am currently still actively using my domain hosts DNS servers whilst I am setting this all up and that is exactly what the dig command is showing.

    systemctl status bind9.service
    Code:
    ● bind9.service - BIND Domain Name Server
       Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
       Active: active (running) since Wed 2019-08-14 17:44:24 NZST; 9min ago
         Docs: man:named(8)
     Main PID: 917 (named)
        Tasks: 35 (limit: 4915)
       CGroup: /system.slice/bind9.service
               └─917 /usr/sbin/named -f -u bind
    
    Aug 14 17:46:37 mx named[917]: network unreachable resolving 'ns10.domains4less.co.nz/A/IN': 2001:67c:1010:13::53#53
    Aug 14 17:46:37 mx named[917]: network unreachable resolving 'ns11.domains4less.co.nz/A/IN': 2001:67c:1010:13::53#53
    Aug 14 17:46:37 mx named[917]: network unreachable resolving 'ns10.domains4less.co.nz/AAAA/IN': 2001:67c:1010:13::53#53
    Aug 14 17:46:37 mx named[917]: network unreachable resolving 'ns11.domains4less.co.nz/AAAA/IN': 2001:67c:1010:13::53#53
    Aug 14 17:46:37 mx named[917]: network unreachable resolving 'ns10.domains4less.co.nz/A/IN': 2001:dce:d453::53#53
    Aug 14 17:46:37 mx named[917]: network unreachable resolving 'ns11.domains4less.co.nz/A/IN': 2001:dce:d453::53#53
    Aug 14 17:46:37 mx named[917]: network unreachable resolving 'ns10.domains4less.co.nz/AAAA/IN': 2001:dce:d453::53#53
    Aug 14 17:46:37 mx named[917]: network unreachable resolving 'ns11.domains4less.co.nz/AAAA/IN': 2001:dce:d453::53#53
    Aug 14 17:46:38 mx named[917]: network unreachable resolving 'corpcomp.co.nz/A/IN': 2404:4800:0:140a::aaaa:213#53
    Aug 14 17:46:38 mx named[917]: network unreachable resolving 'corpcomp.co.nz/A/IN': 2404:3800:f::aaaa:44#53
    This server does have active websites that I can access from outside my local network, so I'm more than a little confused when I see unreachable. But my very limited knowledge isn't helping.

    Server: mx.corpcomp.co.nz (Debian Stretch) ISPConfig 3.1.14p2 (fully updated)
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Search the forum for 'named-checkzone'.
     
  3. FredZ

    FredZ Member HowtoForge Supporter

    Thank you till

    As I have limited knowledge in the aria of DNS I simply added "A" records for the NS servers and problem solved.

    Many thanks for the insite.

    Why would DKIM be greyed out when creating via the wizard?

    Regards

    Fred
     

Share This Page