Hi there
A friend reminded me to use the list, as it is sometimes a bit quiet here. ;-)
My understanding of a glue record is, that the registrar of a domain is responsible to configure them (in my case at home, this was Cyon, but they were a bit puzzled, as they don't do this very often).
Just to understand this technically (I'm perhaps totally wrong): - Domain registrar receives customer order (put dns.xyz.zyx with 1.2.3.4 as glue record into some system) - Registrar has an interface (fax, carrier pigeon or something similar) to tld registry, which can save the record to its database
If I further change my registrar, this doesn't affect that entry, but any change has to be ordered through the new registrar.
There is usually no way to do this myself (if the registrar is not offering such an interface).
Please help or correct me. Thank you.
Urs Müller
SBB AG Cyber Defense Center Poststrasse 6, 3072 Ostermundigen Mobil +41 79 433 21 67 urs.bf.mueller@sbb.ch / www.sbb.ch
Glue Records do exist for domain name servers which are in the same domain.
For example if you have two nameservers:
ns1.example.com ns2.example.com
and your registrar would have entries to resolve example.com like this:
example.com NS ns1.example.com example.com NS ns2.example.com
Then it can't resolve because to resolve the nameserver's names, it has to ask the nameserver for example.com which results in a infinite loop. That's why the addresses of the nameservers have to be hardcoded in the upstream DNS so the downstream can always be resolved.
So the upstream domain must have entries like this:
example.com NS ns1.example.com example.com NS ns2.example.com ns1.example.com. A 1.2.3.4 ns2.example.com. A 4.5.6.7
so the domain name servers can always be found without asking a yet unknown DNS server.
But if you use
example.com NS ns1.some-other-domain.com example.com NS ns2.some-other-domain.com
Then this is not necessary if some-other-domain.com can always be resolved because the IP's of the nameservers are in that zone's DNS.
Now if you port the domain to some other registrar, I presume these glue record entries have to be taken care of by the new registrar as the NS entries is whats going to be managed by your registrar.
This is whats happening on the DNS level. Whats happening on the registrar database level might be a different thing but I doubt that if you take over a domain from Registrar A to Registrar B all the entries in the root zone would automatically be taken over because usually you just remove all entries from the old registrar and the new registrar would put your new entries in (which you have to tell the new registrar).
Mueller Urs SBB CFF FFS wrote on 15.04.21 14:48:
Hi there
A friend reminded me to use the list, as it is sometimes a bit quiet here. ;-)
My understanding of a glue record is, that the registrar of a domain is responsible to configure them (in my case at home, this was Cyon, but they were a bit puzzled, as they don't do this very often).
Just to understand this technically (I'm perhaps totally wrong):
- Domain registrar receives customer order (put dns.xyz.zyx with 1.2.3.4 as glue record into some system)
- Registrar has an interface (fax, carrier pigeon or something similar) to tld registry, which can save the record to its database
If I further change my registrar, this doesn't affect that entry, but any change has to be ordered through the new registrar.
There is usually no way to do this myself (if the registrar is not offering such an interface).
Please help or correct me. Thank you.
Urs Müller
SBB AG Cyber Defense Center Poststrasse 6, 3072 Ostermundigen Mobil +41 79 433 21 67 urs.bf.mueller@sbb.ch / www.sbb.ch
swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Hi Urs
On 4/15/21 2:48 PM, Mueller Urs SBB CFF FFS wrote:
Hi there
A friend reminded me to use the list, as it is sometimes a bit quiet here. ;-)
My understanding of a glue record is, that the registrar of a domain is responsible to configure them (in my case at home, this was Cyon, but they were a bit puzzled, as they don't do this very often).
Yes, the Glue info needs to be updated via the registrar. Many registrars provide a option for this in their control panel, but if that isn't available you have to do this via support case.
Just to understand this technically (I'm perhaps totally wrong):
- Domain registrar receives customer order (put dns.xyz.zyx with 1.2.3.4 as glue record into some system)
- Registrar has an interface (fax, carrier pigeon or something similar) to tld registry, which can save the record to its database
The registrar sends the update via the EPP protocol to the registry. If you're interested in the technical details, you'll find an example in the "EPP Benutzerhandbuch" on https://www.nic.ch/de/registrars/becomeregistrar/ (4.4 "Host commands" host create/host update)
When generating the zone, the registry then checks if it is actually required to write the Glue info into the DNS Zonefile ( in your example, if xyz.zyx actually uses dns.xyz.zyx as its own nameservers)
If I further change my registrar, this doesn't affect that entry, but any change has to be ordered through the new registrar.
no, when a domain is transferred to a new registrar, all domain information such as nameservers and dnssec information stays intact. (At least for .ch./li - not sure if this is the same at every registry)
There is usually no way to do this myself (if the registrar is not offering such an interface).
Correct.
There is a RFC which describes a technology that would allow nameserver operators to signal glue updates to the parent ( "CSYNC", https://tools.ietf.org/html/rfc7477 ), but to my knowledge, no TLD supports this yet
Best regards Oli
-
Andreas Fink -
Mueller Urs SBB CFF FFS -
Oli Schacher