for those of us who are trying to provide dual stack services, how the heck do we get v6 glue added to the gtlds? specifically, i want to add v6 glue for psg.com and rip.psg.com in the com zone.
similarly for the root, as rip.psg.com serves some tlds.
for those of us who are trying to provide dual stack services, how the heck do we get v6 glue added to the gtlds? specifically, i want to add v6 glue for psg.com and rip.psg.com in the com zone.
similarly for the root, as rip.psg.com serves some tlds.
Depends on your registrar. As one of the few ones enom.com can add AAAA glue for at least .com and probably some others.
And NetworkSolutions & Joker.com don't even know what 'glue' means, they think that you want to use their managed DNS services and put AAAA's in there.
Then again NSI doesn't even get the part right that there are people who do not have a phonenumber starting with +1, let alone that some people don't have a fax, thus nicely pushing invalid information into whois.
Some people claim that if you can get through the hoops of the phonesystem at NSI that they can manually add them though.
similarly for the root, as rip.psg.com serves some tlds.
The request has to come from a TLD manager (anyone which uses rip.psg.com)
i can go down the hall to the mirror and ask myself to ask me to do it.
but, of course, you would get a more authoritative reply from IANA.
i am hoping that.
It's the same process that is used to update a delegation in the root zone. For ccTLDs I believe there's some kind of web portal to allow such changes to be requested, but my experience is that the old text form also still works just fine.
I've done this a number of times over the past few years and have not had any problems.
I don't know what the process is for getting IPv6 addresses associated with host records in the VGRS COM/NET registry, but it seems like good information to share here if you find a definitive answer.
It's the same process that is used to update a delegation in the root zone. For ccTLDs I believe there's some kind of web portal to allow such changes to be requested, but my experience is that the old text form also still works just fine.
i actually spent 20 minutes on the iana web site. admittedly that was far to little time to navigate and appreciate the plethora of papers and declarations on this and that. i finally sent off an email, but have no response, yet. i have hope, as the team there now is pretty good. it's probably just my lack of talent at navigating that much layer >= 9 paper. they need a link on the entry page saying "old ops folk go here."
I've done this a number of times over the past few years and have not had any problems.
send url.
I don't know what the process is for getting IPv6 addresses associated with host records in the VGRS COM/NET registry, but it seems like good information to share here if you find a definitive answer.
i will. i am trying to document ops processes for v6 in my feeble way, doing it in a blog-like fashion. e.g. for the sage of doing it at one small set of servers see <http://rip.psg.com/~randy/ipv6-westin.html>. more clues would be appreciated. i am hoping all this will seem trite and passe in six months or so.
but if we can not find a way to get AAAA glue added to gTLDs such as the com zone, we have a *serious* impediment to v6 deployment that needs to be fixed quickly.
It's the same process that is used to update a delegation in the root zone. For ccTLDs I believe there's some kind of web portal to allow such changes to be requested, but my experience is that the old text form also still works just fine.
i actually spent 20 minutes on the iana web site. admittedly that was far to little time to navigate and appreciate the plethora of papers and declarations on this and that. i finally sent off an email, but have no response, yet. i have hope, as the team there now is pretty good. it's probably just my lack of talent at navigating that much layer >= 9 paper. they need a link on the entry page saying "old ops folk go here."
I've done this a number of times over the past few years and have not had any problems.
The .com/.net registry has supported AAAA RRs for over five years
(since May, 2002). The issue you may be encountering is that not
every .com/.net registrar supports them.
i finally sent off an email, but have no response, yet.
Should have gotten a response by now. If not, let me know.
i have hope, as the team there now is pretty good. it's probably just my lack of talent at navigating that much layer >= 9 paper. they need a link on the entry page saying "old ops folk go here."
We've been working on getting a new web site up for quite a while, unfortunately other fires took priority (sigh).
I've done this a number of times over the past few years and have not had any problems.
i will. i am trying to document ops processes for v6 in my feeble way, doing it in a blog-like fashion. e.g. for the sage of doing it at one small set of servers see <http://rip.psg.com/~randy/ipv6-westin.html>. more clues would be appreciated. i am hoping all this will seem trite and passe in six months or so.
As you will (or already have) discover, you are entering a particularly unpleasant area of existing policy, namely dealing with a name server that is shared by many TLDs. We're trying to fix this, but (as with seemingly all things associated with ICANN), it is taking too long.
The .com/.net registry has supported AAAA RRs for over five years
(since May, 2002). The issue you may be encountering is that not
every .com/.net registrar supports them.
way cool.
do you happen to know if opensrs registrars have a path to do so?
The .com/.net registry has supported AAAA RRs for over five years
(since May, 2002). The issue you may be encountering is that not
every .com/.net registrar supports them.
way cool.
do you happen to know if opensrs registrars have a path to do so?