So, I understand that the normal structure for making a domain name operational is as follows:
1. Store one or more NS (nameserver) records for my domain name in a TLD zone file - e.g.,
.com zone file
EXAMPLE NS NS15.DOMAINCONTROL
EXAMPLE NS NS16.DOMAINCONTROL
2. The TLD zone file also includes A (address) records for those nameservers - e.g.,
NS15.DOMAINCONTROL A 97.74.107.8
NS16.DOMAINCONTROL A 173.20.75.8
3. The nameservers each maintain a zone file that includes one or more authoritative A records for my domain name - e.g.,
EXAMPLE.COM 600 IN A 185.132.04.59
Now, here's my question. Is there a way to place the A record for my domain name directly into the TLD zone file?
I understand why this would not be a good idea. My IP address could change, and it would be inefficient to ask Verisign to update the .com zone file any time my IP address changes. Far better to simply point to one or more authoritative nameservers so that I can easily update the zone file on those nameservers if my IP address changes.
But my question is whether it is nonetheless possible to store the A record for my domain name directly into the TLD zone file so that there is no need to redirect to an authoritative nameserver to resolve a DNS query.
I assume that even if this practice were technically possible, the registry wouldn't permit it. In that vein, I assume that registries permit only registrars to access their registry systems in order to request updates to the zone file. And so, the only A records that registrars place in TLD zone files are domain names for authoritative nameservers, not for end user domain names.
Thanks!
1. Store one or more NS (nameserver) records for my domain name in a TLD zone file - e.g.,
.com zone file
EXAMPLE NS NS15.DOMAINCONTROL
EXAMPLE NS NS16.DOMAINCONTROL
2. The TLD zone file also includes A (address) records for those nameservers - e.g.,
NS15.DOMAINCONTROL A 97.74.107.8
NS16.DOMAINCONTROL A 173.20.75.8
3. The nameservers each maintain a zone file that includes one or more authoritative A records for my domain name - e.g.,
EXAMPLE.COM 600 IN A 185.132.04.59
Now, here's my question. Is there a way to place the A record for my domain name directly into the TLD zone file?
I understand why this would not be a good idea. My IP address could change, and it would be inefficient to ask Verisign to update the .com zone file any time my IP address changes. Far better to simply point to one or more authoritative nameservers so that I can easily update the zone file on those nameservers if my IP address changes.
But my question is whether it is nonetheless possible to store the A record for my domain name directly into the TLD zone file so that there is no need to redirect to an authoritative nameserver to resolve a DNS query.
I assume that even if this practice were technically possible, the registry wouldn't permit it. In that vein, I assume that registries permit only registrars to access their registry systems in order to request updates to the zone file. And so, the only A records that registrars place in TLD zone files are domain names for authoritative nameservers, not for end user domain names.
Thanks!