DNS records: TXT BUG

Support
1

Hi,
I’ve encountered what at this point I believe is a bug.
This morning I was trying to edit my TXT for spf to include my invoicing platform.
My intended change was from

v=spf1 include:zoho.com ~all
to
v=spf1 include:zoho.com include:sender.zohoinvoice.com ~all

As per the instructions from Netlify Docs I added the new record, then deleted the old one.
To my surprise, the record would not show up - I waited over an hour to make sure it wasn’t a propagation issue.

What confused me at that point was, even my old TXT records where not showing anymore. I then deleted my TXT records and added a new dummy record
Dummy TTL: 300
This record showed up instantly.

Elated, I added my real records
v=spf1 include:zoho.com include:sender.zohoinvoice.com ~all TTL: 3600
zoho-verification=zb83064522.zmverify.zoho.com TTL: 3600
They showed up instantly.

I then decided to delete my dummy record, and that’s where it got weird.
All of my TXT records were no longer being found. They were still showing in my Netlify DNS Dashboard though.

I’ve come to the conclusion, that deleting any TXT record will make all TXT records with the same host value stop working.

The ‘easy’ fix is to just delete all TXT records with the same @ and then adding them again.

I made this post so that:

  1. Netlfiy can address the issue, if others are affected.
  2. Users running into the same issue can use my workaround.

Tools used for DNS lookup:

https://toolbox.googleapps.com/apps/dig/#TXT/
https://mxtoolbox.com/SuperTool.aspx

Domain Tested:
spacecoastds.com

1 Like
2

Deleting a single record definitely doesn’t delete all records. Something else could have gone wrong here.

3

Thanks @timscds. Same exact thing was happening to me. Deleting all TXT records and adding them again worked. It does feel like a bug to be honest.

1 Like
4

Glad I could help @FedericoDiRosa

I just had to change a txt record for another domain and can confirm its still a problem.
Maybe @hrishikesh can take a look now that I’m not the only one :smile:

5

Hi, @timscds. I tested and confirmed that the described bug does indeed exist. We have filed an issue with our developers to resolve this issue. We will have another update here when the bug is confirmed to be fixed.