ALIAS-Record auf Secondlevel-Domain

Discussion in 'General' started by jackserippl, Sep 9, 2022.

  1. jackserippl

    jackserippl New Member

    Hi all
    A customer of mine is in need of an ALIAS-DNS-Record directly on a Top-Level-Domain. Is that not possible by design or what am I doing wrong? If I enter the ALIAS-Record, zone gets corrupt with an .err-file.

    Error DNS-Zone:
    Code:
    $TTL        3600
    @       IN      SOA     ns01.isp.ch. support.isp.ch. (
                            2022090901       ; serial, todays date + todays serial #
                            7200              ; refresh, seconds
                            540              ; retry, seconds
                            604800              ; expire, seconds
                            3600 )            ; minimum, seconds
    ;
    
    example.com. 3600      CNAME        vgtpibi.azureedge.net.
    cdnverify.example.com. 3600      CNAME        cdnverify.vgtpibi.azureedge.net.
    www 3600      CNAME        www.vgtpibi.azureedge.net.
    example.com. 3600      MX    10   13.69.215.176
    example.com. 3600      NS        ns01.isp.ch.
    example.com. 3600      NS        ns02.isp.ch.
    example.com. 3600      TXT        "v=spf1 mx a ip4:13.69.215.176/32 ~all"
    named-checkzone test
    Code:
    dns_master_load: pri.example.com.err:10: example.com: CNAME and other data
    pri.example.com.err:13: warning: '13.69.215.176': MX is an address
    dns_master_load: pri.example.com.err:16: example.com: CNAME and other data
    dns_master_load: pri.example.com.err:16: example.com: CNAME and other data
    dns_master_load: pri.example.com.err:16: example.com: CNAME and other data
    zone example.com/IN: loading from master file pri.example.com.err failed: CNAME and other data
    zone example.com/IN: not loaded due to errors.
    Any help would be highly appriciated

    best regards
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Your problem is probably this:

    example.com. 3600 CNAME vgtpibi.azureedge.net.

    in combination with:

    example.com. 3600 TXT "v=spf1 mx a ip4:13.69.215.176/32 ~all"

    If I remember correctly, it is not allowed in DNS (not ISPConfig specific btw.) to have TXT records and CNAME records for the same name if CNAME points to an external system. The logic behind that is that you delegate example.com vgtpibi.azureedge.net so a TXT record for example.com must be at vgtpibi.azureedge.net and not in your local zone (at least that's my understanding).
    Try deleting the txt record to see if the error goes away then.
     
    Th0m likes this.

Share This Page