Hi, @ankitgoyal100. I see that you sent me two screenshots of the DNS records in a PM. Unfortunately, I need the actual text data shown in the screenshots.
Now, I could try to type out all 36 DNS record names, types, TTLs, and values by hand but I just don’t have time to do that. Similarly, many of the record names and values are random. The odds of me typing out all the random values correctly is very slim.
So, what I can do is to tell you how I would validate this if I were making this change.
- I would make a list somewhere (maybe in a text file) of all the required DNS records which are currently at Netlify.
- I would then use some sort of programming language I am comfortable with to read the list of required records for that file.
- The program would then query for each DNS record at Netlify. The program saves this information somewhere.
- The program then queries for each DNS record at Cloudflare. The program saves this information as well.
- The program then compares to all three sets of records and reports any Netlify or Cloudflare records that do not match the file.
If not all records are reported as matching, you would then change them until they do match.
When all the Cloudflare DNS records are reported as matching, then the changeover from one DNS service to the other should invisible the users of your site when it happens. There will be no downtime.
If you are looking for tools to use, I personally tend to use
dig for most of my DNS troubleshooting. You can test DNS records directly at Netlify using
dig by including the authoritative name servers for the domain in the dig command like so:
dig the.domain.name.here TYPE @your.nameserver.name
Using a more realistic (but still not real) example:
dig example.com A @dns1.p03.nsone.net.
To query the same record at Cloudflare you might use this:
dig example.com A @dean.ns.cloudflare.com.
You would of course replace
@dean.ns.cloudflare.com with the actual hostname, type, and Cloudflare name server for your domain.
dig tool is a command-line tool which returns very predictable output. Both qualities making it easy to call from other programs/scripts and to parse the information it returns.
For example, you can get just the record itself with the
+answer options like so:
$ dig +noall +answer example.com
example.com. 3875 IN A 184.108.40.206
If there are other questions about this, reply anytime.