IPV6 records not showing up.

Discussion in 'General' started by Hostreps, Jan 14, 2025.

Tags:
  1. Hostreps

    Hostreps New Member

    I have added an AAAA record in the panel. It show on the panel and the backend file /etc/bind/pri.domain.name. But the problem is the hostname is not resolved.
    I tried to ping via ping -6
    Address family for hostname not supported
    , then dig @localhost AAAA domain.
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18578
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 1232
    ; COOKIE: 4f8d7b07b083d1b90100000067868032a0d7b53be691bc3a (good)
    ;; QUESTION SECTION:
    ;domain. IN AAAA
     
  2. pyte

    pyte Well-Known Member HowtoForge Supporter

    That's very little information. Could you share the specific zone in question?
    You might also try using the named-checkzone command to check for any clues about the issue.

    Code:
    named-checkzone domain.tld pri.domain.tld
    
     
  3. Hostreps

    Hostreps New Member

    Code:
    dig @localhost AAAA isp.hostreps.in
    
    ; <<>> DiG 9.18.30-0ubuntu0.24.04.1-Ubuntu <<>> @localhost AAAA isp.hostreps.in
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8318
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 1232
    ; COOKIE: e90744a2a706470d01000000678763d2c3026ba1b0d8f524 (good)
    ;; QUESTION SECTION:
    ;isp.hostreps.in.               IN      AAAA
    
    ;; AUTHORITY SECTION:
    hostreps.in.            3600    IN      SOA     isp1.hostreps.in. admin.hostreps.in. 2025011403 7200 540 604800 3600
    
    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(localhost) (UDP)
    ;; WHEN: Wed Jan 15 07:29:22 UTC 2025
    ;; MSG SIZE  rcvd: 119 
    Code:
     The output for tail -n1 /etc/bind/pri.hostreps.in
    isp.hostreps.in 3600      AAAA       2607:5300:60:167c:0:0:0:1
    
    Do you need any further information, please let met know.
     
  4. pyte

    pyte Well-Known Member HowtoForge Supporter

    Please check with the named-checkzone command.
    Code:
    named-checkzone hostreps.in pri.hostreps.in
    Make sure that there is no zonefile with for `hostreps.in` with an `.err` extension.
     
  5. Hostreps

    Hostreps New Member

    Yeah there is no .err files
    Code:
    
     ls /etc/bind/pri.hos*
    /etc/bind/pri.hostreps.in
    root@isp:~#
    
     
  6. pyte

    pyte Well-Known Member HowtoForge Supporter

    I've already asked twice to check with the named-checkzone command for errors :)
    Code:
    named-checkzone hostreps.in /etc/bind/pri.hostreps.in
     
    ahrasis likes this.
  7. Hostreps

    Hostreps New Member

    Sorry I already posted on my previous response
    Here you go:

    named-checkzone hostreps.in /etc/bind/pri.hostreps.in
    zone hostreps.in/IN: loaded serial 2025011403
    OK
     
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    Ok, so the AAAA is in the zone file, which means there is no issue from ISPConfig's side, but BIND does not returns the record? In this case, it might be that the BIND process is hanging and not loading new changes. Stop bind, check that no named processes are running anymore and then start it again using systemctl command.
     
  9. Hostreps

    Hostreps New Member

    I tried to stop,start reload bind9 and named services but no luck
     
  10. pyte

    pyte Well-Known Member HowtoForge Supporter

    Strange. The only idea I have is to enable logging and verify if the zone is being loaded with the correct serial. Additionally, check the logs for anything unusual or out of the ordinary.
     
  11. remkoh

    remkoh Active Member HowtoForge Supporter

    That can be easily checked online. There are several sites out there to check your dns functionality that also display the serial.
    Compare that serial with the one in the zone file on the server. They should be the same.
    Also there should not be a difference between master and slaves.
     
  12. Hostreps

    Hostreps New Member

    I am sorry, I identified the problem. I entered as isp.hostreps.in instead of isp. This was the problem and now its working. Thank you everyone for helping.

    Please add a feature to enter just the sub domain alone, where it will helpful for others newbies
     
  13. till

    till Super Moderator Staff Member ISPConfig Developer

    You can always just enter the subdomain alone in DNS. But if you enter the complete domain, then it must end with a dot. If you miss adding the dot and use a fully qiúalified domain name, then it can not work.
     
  14. remkoh

    remkoh Active Member HowtoForge Supporter

    Any record not ending with a dot is read as <submitted name>.domain.tld.
    So if you create a record named isp.hostreps.in (without a dot at the end) it will read as isp.hostreps.in.hostreps.in.

    As @till said, you can create a record with just the subdomain as name or a fully qualified domainname (ending with a dot!) as name.
    They are both exactly the same.

    When you create a record with just domain.tld. as name you can enter only @ in ISPC (and any dns server). A lot less typing ;)
     
    till likes this.

Share This Page