this post was submitted on 13 Jun 2023
29 points (100.0% liked)
Technology
37603 readers
572 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A small correction: the registrar directs the registry (on your behalf) to configure the registry's DNS servers to point at whichever DNS servers you specify to host the domain, which default to the registrar's DNS servers. The chain of delegation is most commonly either:
or
Thank you! I didn't know it was like that, but it makes perfect sense.
This is really cool. So if I set my domain's DNS on the registrar's website, that DNS record is propogated to the registry? I have had this change start working in under five minutes. It's insane how fast that is given what is actually being done.
Yes, the registrar controls the NS records (and, if your zone is DNSSEC signed, DS records) for your domain in the zone the registry hosts.
[EDIT: I forgot about this part earlier.] The registrar will typically also give you the ability to "register nameservers", which means specify one or more names within the name space of your domain that you want to act as nameservers and their IP addresses. The registrar will insert A and/or AAAA records into the registry to be used as glue records.
This is probably much further down in the weeds of "how web domains work" than the OP intended.