Assistance Required for Setting Up Klaviyo Sender Domain for madfit.co

[bill47]

Dear Cloudflare support,

I hope this message finds you well. We are in the process of configuring a Klaviyo sender domain for our website, madfit.co. Despite having added all the necessary records as instructed by Klaviyo, we are encountering an issue where the sender domain cannot be activated due to an unknown error.

We have already reached out to Klaviyo’s support team for assistance, and we received a response:

"I’ve run some dig queries on your DNS records, and I was able to narrow this down to a propagation issue. For example, when I run these queries in the Terminal, I can see the proper records returning as a result.

However, when I run them through DNS Checker, we can see the below records are online on the open internet, all over the world.

Whereas the following records (below) are online in most locations, but offline in others.

• DNS Checker - DNS Check Propagation Tool (intermittently going online and offline again)
• DNS Checker - DNS Check Propagation Tool (intermittently going online and offline again)
  Ex.
  
  

In order for us to be able to recognize these records, all of these have to be resolved (e.g. online - green checkmark) on the open internet. From what I can see through troubleshooting this, it appears that these records are intermittently coming online and then back offline; which is currently the reason why you’re unable to move forward with domain activation in Klaviyo.
The best path forward at this time, would be to reach out to your DNS provider to query these propagation issues. You can provide them with my screenshot in addition to the links to DNS Checker and from there, they should be able to determine what’s going on with record propagation and assist with next steps. We are incredibly limited on additional troubleshooting that we can provide given that this is a 3rd party platform and we don’t have access to their back-end system to determine root cause. If the records, for example, aren’t propagating properly nor coming online in order to verify them in our platform, the DNS provider is the next step in order to further assist with getting these online so our system can recognize them.
I hope this helps and if you have any additional questions or concerns, please don’t hesitate to reach back out."

Thank you for your attention to this matter.

[Laudian]

Generally, that answer is a lot of nonsense.

You don’t see the red cross on Byfleet because of any problems with your Cloudflare setup, but because the Byfleet resolver simply isn’t working. I tried cloudflare.com, google.com and a few others, none of them work. It seems the resolver works for A records but not for TXT.

A red cross in Dnschecker is really not a reliable indicator of a problem. It’s just a good way for support to tell you to bother someone else, because the “error” obviously happens for every domain the support agent enters into it, and to an inexperienced user it actually looks like a real problem.

@bill47

and I was able to narrow this down to a propagation issue

Again, complete nonsense. When you query a public resolver for a DNS record, the resolver will cache the result and reuse it for some time. That means that when you change DNS records, your users might still use the old record for some time.

But that is not something that applies here, because for verifying DNS records, you wouldn’t use a public resolver that caches records, but rather your own non-caching resolver.
And even if they do use a public resolver, the TTL for your TXT record is 5 minutes. These 5 minutes have passed many times over before the “support” ever looked at your records.

What records were you supposed to add? Maybe there is some simple problem.

[mcorreia]

@bill47

In order for us to be able to recognize these records, all of these have to be resolved (e.g. online - green checkmark) on the open internet.

Hi there,

This makes no sense. Cloudflare does not own every DNS resolver, so the fact that one is not propagating can’t be seen as our responsibility but the responsibility of the entity running it. Plus the way DNS works makes this a non issue as when not resolving, the resolution skips that and tries the next one.

Try running the same test searching for google.com TXT records for instance:
DNS Checker - DNS Check Propagation Tool

Does google have a DNS issue too or is it 4D Data Centres Ltd?

Take care.