I've setup v6ns.org (http://v6ns.org), a service allowing one to create A and AAAA records and host it on IPv6-enabled nameservers. The intended usage is to create such records for your nameservers, then point your domain(s) to those records.
This is useful when you have a domain with a registrar that does not support IPv6 glue. There are also numerous registries that have some servers (usually managed by external organizations - ISC, RIPE and nic.fr are common ones) with IPv6 connectivity, but don't support AAAA glue.
The v6ns.org zone is currently hosted on 4 geographically distributed nameservers (London, London, Germany and St Louis), 3 of them with IPv6 connectivity.
PIR says that IPv6 for the .org TLD is still under test, so how did you get the IPv6 glue in there?
Did they actually say that, rather than merely not having posted any updates since http://blog.pir.org/?p=19 (http://blog.pir.org/?p=19)? I just asked my registrar (Inwx (http://www.inwx.de/)) to add it, which they did; presumably via a standard registrar->registry interface.
Quote from: PIR.ORG just reached another milestone in its campaign to foster a more robust and secure Internet. Beginning today, July 31, the Internet addressing system known as IPv6 will be deployed for testing, and will shortly be available for full use by registrars.
IMO, ~42 days is more than "shortly".
What are they testing, anyway? The code change should be extremely trivial; of course, some tests should be done, but there's so little to be tested (both in code and number of things to test) that it should be brief.
I'm going to contact PIR about this.
It's merely that they haven't posted anything since stating they were testing. Something important like this would likely have generated a separate blog entry at PIR. In any event, I've complained to my registrar for NOT supporting IPv6 for .org when it appears that they do (and my registrar does support IPv6 for other TLDs).
OK - my registrar turned on IPv6 glue for .ORG today.
For my own .org domain I used the nameservers from one of my .com domains. These nameservers have IPv6 glue, so all is well.
Quote;; QUESTION SECTION:
;example.org. IN ANY
;; ANSWER SECTION:
example.org. 600 IN SOA example.com. root.example.com. 2008062101 10800 900 604800 86400
example.org. 600 IN NS ns1.example.com.
example.org. 600 IN NS ns2.example.com.
example.org. 600 IN A 0.0.0.0
example.org. 600 IN MX 10 mail.example.com.
example.org. 600 IN AAAA ::
;; ADDITIONAL SECTION:
ns1.example.com. 600 IN A 0.0.0.0
ns1.example.com. 600 IN AAAA ::
ns2.example.com. 600 IN A 0.0.0.0
ns2.example.com. 600 IN AAAA ::
mail.example.com. 600 IN A 0.0.0.0
mail.example.com. 600 IN AAAA ::
That's not glue - as it's out of zone. Example.com and example.org are disjoint.
nic.v6ns.org doesn't seem to be working correctly at the moment, I think, or else I'm using it wrong. After entering 'x' in the subdomain, and 'y' as records with A and AAAA records, I should get the relevant records back when I do 'dig ANY y.x.v6ns.org. @ns0.nic.v6ns.org.', right? I've done that, and I'm not getting any results back. Perhaps the server needs some attention over the holidays?
It's working now, and has been for a few days. I'm unsure what happened, but my logs show that nsdc rebuild failed - I suspect a stale lock file. I'm monitoring the situation and periodically testing v6ns.org; I don't anticipate further problems, but since I still don't know what caused it, I can't be sure whether there will be any.
How long should I expect it to take between submitting the form and being able to dig the new entries?
Thanks
i've just create aaaa pointer in v6ns.org, pointing to my to ipv6 enabled nameservers.i can ping both nameserver ns(1|2).*.v6ns.org from outside.
so, do i just have to add those nameservers to my "don't support ipv6 glue record" registrar ;D ?
thank you. :)
Quote from: tcuji on September 11, 2008, 02:33:47 PM
I've setup v6ns.org (http://v6ns.org), a service allowing one to create A and AAAA records and host it on IPv6-enabled nameservers. The intended usage is to create such records for your nameservers, then point your domain(s) to those records.
This is useful when you have a domain with a registrar that does not support IPv6 glue. There are also numerous registries that have some servers (usually managed by external organizations - ISC, RIPE and nic.fr are common ones) with IPv6 connectivity, but don't support AAAA glue.
The v6ns.org zone is currently hosted on 4 geographically distributed nameservers (London, London, Germany and St Louis), 3 of them with IPv6 connectivity.
Unfortunately not all registrars will let you assign glue records for your domain unless the glue is actually registered directly with the registry. I did initially try to use records in v6ns.org for my domain (chaz6.com), but I was not able to,. In the end I had to ask Ardya to register glue records for me with his own registrar.
I was however able to use v6ns.org records for domains in ip6.arpa delegated from SixXS.
Following is the response I received from Gandi on the subject of registering out-of-bailiwick glue, copied verbatim:-
The reason why the registry is not accepting your DNS is because the registry PIR does not have your
glue records registered:
dig @TLD3.ULTRADNS.org.ns2.chaz6.v6ns.org A
dig: couldn't get address for 'TLD3.ULTRADNS.org.ns2.chaz6.v6ns.org': not found
You will therefore first need to assure that you have administratively declared your host at the
registry level, and then, once it has glue records, you will be able to apply it to your domain name
as desired.
(Yes, they made a mistake by substituting a period for a space, though the outcome would have been the same in any case. Yes their system is flawed because it requires at least an A record in addition to AAAA. Maybe someday they will fix it.)
why did you use v6ns.org when your registrar is suporting for ipv6 glue directly?
isn't it more simple just build your own nameserver, then register it at gandi plus ipv6 glue record?(using vmware, if don't want provide additional hardware)
if i'm not mistaken what tcuji meant.he build v6ns.org to provide unsupported ipv6 glue record at registrar.v6ns.org just pointing AAAA record to our own nameserver(which is using ipv6 pointed by v6ns.org AAAA record).then we just add ns(1|2).*.v6ns.org to authoritative nameservers list at "unsupported ipv6 glue record" registrar. cmiiw
now the question is, is it realy work for the sage certification test? are these out-of-ballywick things need to supply ipv6 glue record at "unsupported ipv6 glue record" registrar?i'm confused ;D , this is realy chickens-and-eggs things for me.
would someone kindly give enlightenment to us :)
TIA
note: it doesn't work sage test still need glue record for ns(1|2).*.v6ns.org. at TLD .
Quote from: chaz6 on July 26, 2009, 06:16:52 PM
Unfortunately not all registrars will let you assign glue records for your domain unless the glue is actually registered directly with the registry. I did initially try to use records in v6ns.org for my domain (chaz6.com), but I was not able to,. In the end I had to ask Ardya to register glue records for me with his own registrar.
I was however able to use v6ns.org records for domains in ip6.arpa delegated from SixXS.
Following is the response I received from Gandi on the subject of registering out-of-bailiwick glue, copied verbatim:-
The reason why the registry is not accepting your DNS is because the registry PIR does not have your
glue records registered:
dig @TLD3.ULTRADNS.org.ns2.chaz6.v6ns.org A
dig: couldn't get address for 'TLD3.ULTRADNS.org.ns2.chaz6.v6ns.org': not found
You will therefore first need to assure that you have administratively declared your host at the
registry level, and then, once it has glue records, you will be able to apply it to your domain name
as desired.
(Yes, they made a mistake by substituting a period for a space, though the outcome would have been the same in any case. Yes their system is flawed because it requires at least an A record in addition to AAAA. Maybe someday they will fix it.)
yayyy, i've finnaly remember that i have unused domain at gkg.net, added ipv6 AAAA glue on this domain,make this domain as authoritative nameserver for my domain, run the sage test, and voila, test is passed ;).
thank you everyone. :) especially Alex Broque for pointing me to the right direction.
these all fun and educating people :)
Quote from: leenoux on July 26, 2009, 07:14:42 PM
why did you use v6ns.org when your registrar is suporting for ipv6 glue directly?
Because it does not support ipv6 glue ;) I tried and tried and tried, went several rounds with their support but in the end got nowhere.
my current registrar is also not suporting ipv6 glue record,Alex told me that i could use "out of ballywick" nameserver.where you
use other NS outside of your domain TLD at the registrar, as authoritative NS for the domain.
for example:
my previous ns are:
ns1.triplegate.net.id
host1.triplegate.net.id
both ns hosted at unsupported ipv6 glue registrar.and also those nameservers not ipv6 enabled.
i have domain at gkg.net registrar which is supporting for adding both ipv4/ipv6 glue record.i named it ns3.triplegate.com i put both ipv4/ipv6 glue record.
i added ns3.triplegate.com as authoritative ns(slave) for my domain TLD at my unsupported ipv6 glue registrar.now my authoritative ns are:
ns1.triplegate.net.id
host1.triplegate.net.id
ns3.triplegate.com
if there is native ipv6 query from others resolver for my domain TLD , ns3.triplegate.com will answer those query, since it has ipv6 glue record ,authoritative for my domain TLD(slave ns) and also ipv6 enabled.
#dig aaaa ns3.triplegate.com @a.gtld-servers.net +short
2001:470:19:13c::f
note: i'm sorry chaz6, i think i'm not connected to what you've said before.i thought you've had trouble with ipv6 glue record things.i've read again your post.you have problem with your registrar for not supporting ipv6 glue.that's my problem too untill now ;D , i'm asking their technical support and got clueless answer hehehe...well, as long as there's workarround, it doesn't realy matter for me ;)
Quote from: leenoux on July 27, 2009, 05:53:01 PM
note: i'm sorry chaz6, i think i'm not connected to what you've said before.i thought you've had trouble with ipv6 glue record things.i've read again your post.you have problem with your registrar for not supporting ipv6 glue.that's my problem too untill now ;D , i'm asking their technical support and got clueless answer hehehe...well, as long as there's workarround, it doesn't realy matter for me ;)
In my case the registrar does not support out-of-bailiwick glue unless the glue is registered with the registry - it is not simply enough that the name resolves. Good luck with your registrar!
Sorry to bring up such an old thread but I felt obliged to given the circumstances...
Having waited for far too long for my registrar (Easyspace) to allow the insertion of IPv6 glue records into my parent domain I decided to work around the problem by purchasing another domain with a registrar I knew supported v6 and delegating at least one of my NS records to a name within its bailiwick... My domains would then have at least one delegation entry with a corresponding AAAA record for v6-only clients (and HE Sage certification! ;)).
So... I pondered what I wanted to call the domain and figured that I wanted a generic v6-related domain and having considered a few options I settled with v6ns.org. I bought the domain, set up BIND for it, arranged the secondaries and that was that.
Imagine my surprise (and confusion) when I immediately started getting repeated queries for records within the domain - not random or obvious inquisitive ones - but specific, clearly selected/chosen, sub-domains and records. I did some Googling for v6ns.org and found this post on this very board and panicked that maybe I was stepping on somebody's toes here.. :o
I've tried to get in touch with Tcuji but his/her registered e-mail address no longer appears to be valid (funnily enough, it's in a domain (a different one) that also no longer exists) and so I thought I ought to post here not only for Tcuji's benefit in case I've inadvertently taken over their domain (perhaps it was accidentally left to expire?) but also in case anyone was still relying on this domain for some of their glue. I've been unable to ascertain when the domain expired - my purchase has overwritten all the existing WhoIs info for it and searching for other info doesn't bring up much either.
Given my intention for the domain was to provide my own domain(s) with a means to support a v6-only pathway for DNS resolution I would of course, in the absence of a request to the contrary, be happy to do likewise for anyone else that might desire AAAA (and A if required) records pointing to their v6-enabled NS's, to which they can reference in their parent's delegation records without the need for them to enter IPv6 glue via their registrar. The zone is hosted on three v4/v6 dual-stacked nameservers based in the UK, France and USA.
Mathew