I have created 4 NS records pointing to ns1.klaviyo.com through ns4.klaviyo.com for the subdomain. My DNS mode is ‘Full’. Klaviyo is unable to verify the delegation and I cannot resolve the namesevers for the subdomain.
What steps have you taken to resolve the issue?
Ran dig -4 +trace +nodnssec send.motorcrowd.com.au to confirm it does not work.
Waited 4 days after initially adding the records, confirmed it is still not working.
Today (a few hours ago) I have removed and re-added all records. Still not working.
What feature, service or problem is this related to?
DNS records
What are the steps to reproduce the issue?
Add NS records for a sub-domain of a domain where DNS is managed via Cloudflare.
Works for me, but the Klaviyo nameservers don’t respond for the domain:
dig +trace +nodnssec send.motorcrowd.com.au
...
motorcrowd.com.au. 3600 IN NS nina.ns.cloudflare.com.
motorcrowd.com.au. 3600 IN NS derek.ns.cloudflare.com.
;; Received 107 bytes from 65.22.199.1#53(t.au) in 8 ms
send.motorcrowd.com.au. 3600 IN NS ns1.klaviyo.com.
send.motorcrowd.com.au. 3600 IN NS ns2.klaviyo.com.
send.motorcrowd.com.au. 3600 IN NS ns3.klaviyo.com.
send.motorcrowd.com.au. 3600 IN NS ns4.klaviyo.com.
;; Received 134 bytes from 108.162.192.136#53(nina.ns.cloudflare.com) in 2 ms
;; Received 40 bytes from 205.251.196.237#53(ns4.klaviyo.com) in 1 ms
Thanks a lot @Laudian
I think it’s correct that Klaviyo isn’t yet responsing, because they would most likely not configure things on their side until they verify the NS entries exist.
I can now see a response if I run the dig command from within a VPS, but get an empty response from my own local machine, I would guess that’s a DNS propagation timing issue.
However, those entries were added several days ago now, and if I run the check at https://dnschecker.org/#NS/send.motorcrowd.com.au only very few servers are responding with valid results. I would expect this to have propagated to most of the servers across the world by now?
That is completely up to them, but the NS records definitely do exist.
That is likely a configuration issue with your local machine.
The servers that have valid results are wrong, because there are no authoritative NS records yet. These would have to be configured on the Klaviyo nameservers.
Thanks for all the replies.
I have confirmed that the issue is not with Cloudflare or NS, but the way that the subdomain had been configured in Klaviyo.
I was able to confirm my incorrect suspicions that it was a DNS/Cloudflare issue, incorrectly, when I couldn’t get the dig command to return the 4 NS records from my own machine.
Now that I got access to the Klaviyo account and was able to correct the subdomain, it is working.