You are over thinking things.
DNS is intended to be a distributed service that works off of cached information.
Don't change DNS records often, and use longer-lived TTLs to allow ISPs and other networks to properly cache your DNS info after an initial request for a host name is made. This way, almost all requests should be handled by a almost-local-to-...
Regarding those tests/benchmarks specifically, the resulting response times will largely be a measure of network latency between their benchmark host(s) and your authoritative nameserver(s).
This may not be particularly relevant, for several reasons:
The response time from your authoritative server essentially matters for the cold cache scenario. This ...
Basically if you need some local domain for your office (eg devserver.mydomin.name), then only use local DNS. In your particular case, it is not necessary. It doesn't matter there is 100 or 1000 staff, google public DNS will easily handle. As there is no server in your office why to increase cost by adding physical hardware?
You have duplicate entries for ORIGIN @ (load balancing method called Round-robin DNS):
magiccompetitions.com. 14400 IN A 184.108.40.206
magiccompetitions.com. 14400 IN A 220.127.116.11
whereas the subdomain www only has one:
www.magiccompetitions.com. 14400 IN A 18.104.22.168
This means that it works for everyone who ...
Is there any way to get it to update without reloading Nginx?
Short answer: No.
Long answer: Reloading of Nginx is already a good approach. Alternatively you can establish a VPN connection which reconnects to your backend system in case it's IP address has been changed.
So keep in mind that the command ping is IPv4 only and thus will only ask for A records to resolve. ping6 will request AAAA. A utility like curl or wget should be a better bet in requesting A and AAAA simultaneously. This would be the simple answer to your question if it's the case...
PS: I see you have two DNS servers specified, one running on your ...