Slow Propagation TX MX

Website, Application, Performance DNS & Network
1

I’m coming from AWS Cloud 53 who is still my registrar and using Cloudflare for DNS routing. I setup basic account on cloudflare. My reason for switching was primarily for maintaining a custom e-mail address on my domain. I’m a lightweight with DNS. I’m based in Atlanta.
Two Questions:

  1. After 48 hrs the propagation seems very incomplete (see attachment image), although my e-mail is receiving e-mails, not sure if I’m missing any, and I can access my domain site. I created a new account with Dreamcloud for new e-mail hosting.
  2. Are their benefits to switching my Registrar to Cloudflare or does it not matter that DNS and registry are different?

propo

3

Lots of resolvers not resolving while a few do is typical of DNSSEC not being updated after changing your nameservers.

What is the domain?

3 Likes
4

ppazone .c o m When I switched I was pushed to setup DNSSEC and don’t have a clue what it is. Should I revert off of DNSSEC?

5

Yes, it’s a DNSSEC issue…
https://cf.sjr.org.uk/tools/check?ab200fd0687440d79f1e261704d5dbae#dns

Either switch off DNSSEC at your registrar, or set the DS records at your registrar to match with those from Cloudflare here…
https://dash.cloudflare.com/?to=/:account/:zone/dns/settings

2 Likes
6

Thank you - great info - Would any of this be resolved by moving registration to cloudflare?

7

I see this on my account at CF. Does this mean I’m not pointing correctly from AWS?

8

DNSSEC

DNSSEC uses a cryptographic signature of published DNS records to protect your domain against forged DNS answers.

DNSSEC is pending while we wait for the DS to be added to your registrar. This usually takes ten minutes, but can take up to an hour.

9

A DS Record > option should appear in the DNSSEC box. Press that and copy the record to AWS wherever DNSSEC is enabled there.

1 Like
10

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.