All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
How DNS Resolvers work ??
Hello,
I was searching & trying to learn about DNS Systems but not getting much information.
Suppose, I setup 4 DNSOnly Servers in 3 Different regions e.g. US, EU (2), APAC. I set them as following:
ns1 = us
ns2 = eu
ns3 = eu
ns4 = apac
or,
ns1 = us, eu (2 ipv4 in 1 nameserver)
ns2 = eu, apac (same as above)
If the visitor is from India/Singapore, will it resolve from the APAC Region server ?? Or, it can take any of the 4. If the visitor from India gets the domain resolved from us dns server, then there should be no advantage.
Also, I want to how Domain resolves from a visitors internet browser. Can anyone explain it in a sequencial form ?? I mean, I know that how it is done but when there is more than 1 nameserver & the zones are different then how is it done ??
Regards.
Comments
You need CDN then
No, I just need that the visitor gets resolved from the nearest DNS Server for Domain Resolving. It can be done using AnyCast DNS, but can't find out any AnyCast DNS Supporting cPanel.
The DNS resolver could use any of the authoritative nameservers, because they don't know which one is closer to them.
Last month I did a test: I setup a domain with one NS record that has both IPv4 and IPv6. I observed that the Google DNS resolver was sending two packets from different source address to each IP address listed as authoritative nameserver.
I believe if you have multiple NS records, the Google DNS resolver would send to every IP address at the same time. In that case, your nearest authoritative nameserver would satisfy the query.
As I understand DNS - the majority of systems send 'parallel' requestes to all NS servers. The first one to answer is used. Normally the first reply is the closest or alternatively is the least busiest.
Some systems can however send 'sequentially' to NS servers so order can be significant.
See https://archive.nanog.org/meetings/nanog54/presentations/Tuesday/Yu.pdf
In order for it to pick the resolver closest to the visitor, you will have to configure Anycast. This is more of a networking issue rather than DNS.
There is also GeoDNS using which the DNS server can provide the visitor with name servers in their region.
A full DNS resolution starts with SOA record for that domain name starting with the root name servers which are glue records. That follows the query for NS records (usually included as part of SOA record query). That usually follows a query for A and AAAA records which provides the IP address(es) to contact to obtain the website content using HTTP(S) protocol. Here is an example of how cnn.com would resolve:
https://dynu.com/en-US/NetworkTools/Delegation?Host=cnn.com
To setup Anycast, you must have a class C IP address from ARIN. You can then advertise the same range at multiple locations and have the BGP configured so the closest routes can be picked up. There are some VPS providers who can assist you with the setup of BGP along with Anycast. The DNS server itself is not aware of the Anycast. Anycast is more of a traffic routing method.
A very good example of Anycast is Google.com.
For CNN.com, the last thing they got is their nameserver which they use awdns. There were 4 of them. I wanted to know from which one they got the resolving IP / A Record, or how that gets done.
I would say the best way for DNS that is best in all locations is one of these options
The browser will take the first A/AAAA record from the list. The DNS servers usually rotate the record results to ensure Round Robin results which ensure load balancing. The following command will show the same result but in different order each time.
nslookup cnn.com