DNS Error after Server rebuild

Discussion in 'Server Operation' started by Tastiger, May 24, 2017.

  1. Tastiger

    Tastiger Member

    Due to major failure with my 16.04 server, I had to rebuild from scratch, got it all setup and re-imported my dbispconfig.sql and everything seems to work fine apart from 1 zone, I have tried deleting it and creating it again but no joy - I just get a pri.polyfidelity.org.au.err in etc/bind.

    Checked named.conf.local and the zone isn't in there.

    Was working fine with ISPConfig 3.1.2, so not sure if it is anything to do with the upgrade to 3.1.3? But I would have thought it would have affected all zones if that was the case.

    Here is the content of the pri.polyfidelity.org.au.err (domain keys left out):-
    any suggestions?
     
  2. ahrasis

    ahrasis Active Member

    pop3 line, mail domain is not ending with a dot, is that correct?
     
  3. Tastiger

    Tastiger Member

    Tried adding one but no difference in results - also checked one of the working zones and that has no "." after the domain in the pop3 (see below) - so it's still a mystery.
    Working DNS Zone :-
     
  4. Tastiger

    Tastiger Member

    I can only think that the issue may be down to my interfaces setup and broadcast address. My interfaces is as follows:-
    Is the broadcast address correct?; as a dns check shows no name servers for any of my sites
     
    Last edited: May 26, 2017
  5. Tastiger

    Tastiger Member

    nice try, but still no cigar.
    Until I get that zone up and running the other hosts will not resolve and I just can't see why it is throwing errors from the DB restoration, I've driven myself stupid googling with no joy........

    Anyone with any other clues? - please I am desperate here......
     
  6. Tastiger

    Tastiger Member

  7. Stephan Ververda

    Stephan Ververda New Member

    Yes your interface is correct. In a 24 bits subnet (255.255.255.0) the network is always .0 at the end and the broadcast always .255

    You have 3 problems though with your DNS records, and for the biggest part its the nameserver A records

    So basically there is a problem with lacking dots at the end of the fqdns ns1.polyfidelity.org.au. and ns2.polyfidelity.org.au.
    You also have the same problem in the cname record with mail.polyfidelity.org.au. (also a trailing end)

    To elaborate on that. If a host name or even a fqdn does NOT have a trailing dot then the nameserver will append the domain to it.
    So ns1.polyfidelity.org.au will suddenly become ns1.polyfidelity.org.au.polyfidelity.org.au. So basically you write hostnames without trailing dot and fqdn's with trailing dot.
    So it should be:
     
  8. Tastiger

    Tastiger Member

    Thanks for that clarification.
    Everything is resolving fine after changing the
    to just
    should it matter that I do not have the whole "ns1.polyfidelity.org.au" as I gather from your post it should work provided I do not have the dot after ns1?
    It seems as if somewhere along the line in exporting the sql's the "."s have been added - how I do not know.

    Bookmarking this thread for future reference.
     
  9. Stephan Ververda

    Stephan Ververda New Member

    No it's just fine like that, either using ns1 and let the nameserver add the domain name or use the fqdn followed by a trailing dot will yield the same result.
     

Share This Page