Sometimes you can get around such limitations by having the name of your authoritative DNS server under an entirely different TLD. Your DNS server doesn't need to have a nice looking name. There are plenty of possibilities to get a subdomain for free if you don't mind it having a few more levels of labels than your other names. For example there are multiple providers of dynamic DNS where you get a subdomain for free, you just need to find one with proper dual stack support.
The problem here is it implies that the registry is the one that doesn't support the glue, but in my case (.ca) it does. It is the registrar that is being probitivie and blocking input of AAAA addresses (For glue) into the registry.
Further, utilization of dynamic DNS inserts another cog into the machine that has to be trusted. I would rather keep DNS operations exclusively between my organization's systems and the TLD servers, not bringing some blah.dyndns.org name into the equasion that could get compromised.
In the past, I've changed registrars specifically over this issue - the old registrar not supporting IPv6 glue. I'm now with a registrar which accepts IPv6 glue for EVERY TLD they support, even if IPv6 is not supported in the registry. (For .NAME, the registry doesn't even have IPv6 addresses for its TLD servers!)
Every registrar should support IPv6 glue. Those who don't are clueless.
Agreed, though the question arises: Is there a list of registrars for each registry somewhere and their v6 support? (similar to http://bgp.he.net/report/dns/
) If not, such compilation would be interesting to see. I'll explain:
Considering it is the registrars who are the frontline to the TLDs and that registrants don't have direct access to the registry, that should be the gauge of IPv6 support to the registry — not just whether the registry accepts AAAA glue and has servers operational with v6 addresses (as that is trivial for the registry to deploy). This would also call on registries to possibly eventually "ditch" refusenik registrars who ignore or insist IPv6 isn't coming or are being extremely slow to deploy.