Is there a better way to set up DNS at the registrar?

[GoWilkes]

I have about 70 domains parked on top of a main domain. I have all of them set to the same nameservers, then use cPanel to park them on top of that main domain.

My registrar has DNS settings, though, which allows me to enter DNS records at the domain and not have to ping the server. I'm testing one domain and set the A record for foo.com and www.foo.com to point to the server, then a CNAME for mail and ftp, then a TXT for SPF1 and copied the DKIM from cPanel.

Is there a speed/performance/other advantage to doing this for all of my domains?

If so, are there any other steps that I can skip in the process? I assume that I still have to park every domain manually, but do I have to manually copy the DKIM's p value for each domain?

 

[quietFinn]

Personally, I would not do all that extra work to add dns records manually when cPanel does it automatically, the only difference is that you use registrar's nameservers instead of your own. If your nameservers work there can't be any significant difference in speed or performance.

 

[kssuhesh]

If you are using the name servers which is pointing to the cpanel itself, it will manage everything like adding a subdomain, change in site IP etc.. But if you are using remote name servers ( like registrar name servers or Cloudflare name servers ) , then you should need to replicate the same entries ( like in the case of DKIM) from cpanel to name servers.

 

[GoWilkes]

My thought was that it may shave a few milliseconds off of every page view if the domain doesn't have to ping the server to figure out the DNS. I've been micro-optimizing for awhile now, when I discovered that shaving 10ms here and 20ms there was adding up! By now I've cut my load time in half, which has resulted in more pages per session.

But I'm really not sure if this one would shave off any additional load time, or if it'd be a big waste of time :-/

 

[cPRex]

That isn't how DNS works. DNS doesn't always "ping" the actual nameserver as the records are cached around the world. That's why propagation has to happen after every DNS change, as all the other servers around the world pick up on the record as the TTL expires.

So, while the theory is sound that a bigger/scarier nameserver could be faster, it likely isn't the case unless you have an extremely busy nameserver system due to how caching works.