Adding TXT record breaks domain name resolution

rinkleton

• January 02, 2026 06:57

I have a DNS zone (lets call it example.com).  It has a star subdomain record of "*.d11" (CNAME).  So you can ping something like "example2.com.d11.example.com" and that works fine.  But I renew some Let's Encrypt certs with the DNS verification so it adds a TXT record like:

_acme-challenge.www.example3.com.d11    1    IN    TXT    "CODEHERE"

For whatever reason, while that text record exists, anything ending in "com.d11.example.com" can't be resolved and doesn't ping.  So "example4.com.d11.example.com" doesn't work.  However "example4.net.d11.example.com" does work.  

I'm not a DNS expert, but as far as I know, adding a text record shouldn't affect pinging.  Am I missing something?

• 

  cPanelPeter cPanel Staff

  • January 02, 2026 19:29

  Hello, 
  
  I'm curious how you added a *.d11 CNAME as a subdomain record... Have never heard of something like that.

   

  0
• 

  rinkleton

  • January 03, 2026 04:31

  Here is the full record for that:

  *.d11    14400    IN    CNAME    sub.example.com.

  0
• 

  cPRex Jurassic Moderator

  • January 05, 2026 13:40

  I don't have a logical explanation for why just .com wouldn't work when .net works in your example.  It might be best to create a ticket so this can be seen in action.

  0

Please sign in to leave a comment.