DNS proble : Alias not resolved

Discussion in 'General' started by HitoDev, May 31, 2018.

  1. HitoDev

    HitoDev Member

    Hello

    This mail because since a few days alias created with ispConfig are ignored.

    Usually I create an alias (aliasdomain) and a CNAME or ALIAS record in the DNS of the target site and it works perfectly.

    Since few days this method doesn't work anymore for one of my domain (domain.net)
    I can create records but, even after more 48 hours, ping to alias.domain.net never respond.

    When I dig alias.domain.net, there is no A records :

    -------------------------------------------------------------------------

    ; <<>> DiG 9.9.5-9+deb8u11-Debian <<>> notworking.domain.net
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5172
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;notworking.domain.net. IN A

    ;; AUTHORITY SECTION:
    domain.net. 3600 IN SOA nsXXXXXX.ip-XX-XX-XX.eu. dev.domain.net. 2018041904 7200 540

    604800 3600

    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Wed May 30 20:24:13 CEST 2018
    ;; MSG SIZE rcvd: 109

    -------------------------------------------------------------------------

    For the working alias dig returns A records (with similar configuration in ispConfig) :

    ; <<>> DiG 9.9.5-9+deb8u11-Debian <<>> working.domain.net
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18626
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;working.domain.net. IN A

    ;; ANSWER SECTION:
    working.domain.net. 3600 IN CNAME domain.net.
    domain.net. 3600 IN A XX.XX.XX.XXX


    ;; AUTHORITY SECTION:
    domain.net. 3600 IN NS sdnsX.ovh.net.
    domain.net. 3600 IN NS nsXXXXX.ip-XX-XX-XX.eu.


    ;; ADDITIONAL SECTION:
    nsXXXXXX.ip-XX-XX-XX.eu. 23658 IN A XX.XX.XX.XX

    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Wed May 30 20:25:44 CEST 2018
    ;; MSG SIZE rcvd: 150

    -------------------------------------------------------------------------


    Something seems "broken" with the website. I guess ispConfig doesn't make its job correctly for domain.net, but I cannot find a way to investigate...
    What should I inspect ?
     
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Did ISPConfig create DNS record when alias domain was created? I assume it is necessary to create A record or CNAME myself, but can not check now while on my tablet computer.
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    Is the cname record shown in the zone details in ISPConfig? If yes, then take a look at the created dns zone file to check if it is in that file as well.
     
  4. HitoDev

    HitoDev Member

    Yes, absolutely : added aliasdomain and CNAME records are recorded. I even verified the records data are similar to previous in phpMyAdmin.
    Maybe ispConfig doesn't write something in a file ?
    Or a service needed service shutdown ?

    Thank you for your replies.
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    That's what I asked you to verify. Take a look at the zone file to see if the records appear there. On Debian and Ubuntu, these files are in /etc/bind/ folder.
     
  6. HitoDev

    HitoDev Member

    /etc/bind/

    I have :

    pri.domain.net:
    Missing records in pri.domain.net for all non-working aliases

    pri.domain.net.err
    File is identical excepting for one entry:

    apps.domain.net. 3600 CNAME domain.net

    This entry is in pri.domain.net and not in pri.domain.net.err

    I note a missing "." after "domain.net"
    I'm doing the correction and test again.

    Thanks
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    A .err file is created when bind rejects the new config. you can see the error message from bind with the command named-checkzone.

    example:

    named-checkzone domain.net /etc/bind/pri.domain.net.err
     
  8. HitoDev

    HitoDev Member

    OK, trhe missing dot was the reason of the problem :)
    I'll add the exploration of these files to my checklist.
    Thank you very much for your direction and your time !
     
    Last edited: Jun 1, 2018

Share This Page