Hi all,
I've a big problem with my current Registrar Arsys.es. We are turning our Name Server's into an "Multi-homed" environment. Each of our name servers have now two IPs. To use this environment it is necesary to update the glue records in the gTLD accordingly.
<snip> RFC1912 2.3 page 4
If your nameserver is multi-homed (has more than one IP address), you
must list all of its addresses in the glue to avoid cache
inconsistency due to differing TTL values, causing some lookups to
not find all addresses for your nameserver.
</snip>
If we don't update this records, all the multihoming features would just not be used due to that nobody would find our name servers on the additional IPs. But it seems that our registrar does not know nothing about multiple A records per name server and tells us to define 4 name servers, what is definitively not what we want.
My question is if someone had also gone through this problem and if they could solve it with some other registrar. In fact we spoke with the hostmaster from the gTLD servers, Piet Barber from VeriSign, and he confirmed us that there exist many domains with such a configuration but that the update of these records must be done through a registrar. (an example domain with the "biggest" configuration he could find is chndns.com)
Our wished configuration is as follows:
Thanks in advance for your help,
Eric Janz
I've a big problem with my current Registrar Arsys.es. We are turning our Name Server's into an "Multi-homed" environment. Each of our name servers have now two IPs. To use this environment it is necesary to update the glue records in the gTLD accordingly.
<snip> RFC1912 2.3 page 4
If your nameserver is multi-homed (has more than one IP address), you
must list all of its addresses in the glue to avoid cache
inconsistency due to differing TTL values, causing some lookups to
not find all addresses for your nameserver.
</snip>
If we don't update this records, all the multihoming features would just not be used due to that nobody would find our name servers on the additional IPs. But it seems that our registrar does not know nothing about multiple A records per name server and tells us to define 4 name servers, what is definitively not what we want.
My question is if someone had also gone through this problem and if they could solve it with some other registrar. In fact we spoke with the hostmaster from the gTLD servers, Piet Barber from VeriSign, and he confirmed us that there exist many domains with such a configuration but that the update of these records must be done through a registrar. (an example domain with the "biggest" configuration he could find is chndns.com)
Our wished configuration is as follows:
Code:
example.com. IN NS ns1.example.com.
IN NS ns2.example.com.
ns1.example.com IN A 1.1.1.55
IN A 2.2.2.55
ns2.example.com IN A 1.1.1.56
IN A 2.2.2.56Thanks in advance for your help,
Eric Janz
Last edited:
