Opened 9 months ago

Closed 9 months ago

#13617 closed Bug/Something is broken (fixed)

DNS not propogating for

Reported by: Owned by:
Priority: High Component: Tech
Keywords: Cc: k054
Sensitive: no


Hey There folks,

We noticed some DNS records we added a few hours ago are not propagating even when we query being the main one we need

Change History (6)

comment:1 Changed 9 months ago by

  • Cc k054 added

comment:2 Changed 9 months ago by

  • Priority changed from Medium to High

comment:3 Changed 9 months ago by

  • Owner set to
  • Status changed from new to assigned

Let's get jamie to look at this.

comment:4 Changed 9 months ago by

I'm taking a look now. knot is complaining about a semantic check failing on your zone file...

comment:5 Changed 9 months ago by

  • Resolution set to fixed
  • Status changed from assigned to feedback

Can you try again? It should be working now.

The problem was that our DNS server is quite strict about CNAME. If you set a domain (like to a CNAME then knot knows that anytime someone requests that domain name it will return the results of the CNAME.

A problem arises if you try to configure a domain name to be a CNAME and you define something else (in your case, you set a AAAA record for Knot refuses to load it because if someone requests the AAAA record for knot doesn't know whether to deliver the AAAA record you have defined or the AAAA record of the CNAME domain.

To immediately resolve the problem I just disabled your AAAA record for

We have a validation rule that is supposed to stop you from entering a CNAME record for a record that already exists.

But I think it failed because there is no check in the opposite directory (to prevent you from adding an AAAA record for a domain that already has a CNAME).

comment:6 Changed 9 months ago by

  • Status changed from feedback to closed

See #13618

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.