Stuck at Sage test with networksolutions.com.

[InnaGrushevsky]

Hello guys.

I've passed successfully the Guru test, but now I'm stuck at the Sage one.  My domain is electronicnyipv6.net

j:\dig>dig NS electronicnyipv6.net @a.gtld-servers.net
; <<>> DiG 9.3.2 <<>> NS electronicnyipv6.net @a.gtld-servers.net
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 930
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 4
;; QUESTION SECTION:
;electronicnyipv6.net.          IN      NS
;; AUTHORITY SECTION:
electronicnyipv6.net.   172800  IN      NS      a.ns.hosthaus.com.
electronicnyipv6.net.   172800  IN      NS      b.ns.hosthaus.com.
;; ADDITIONAL SECTION:
a.ns.hosthaus.com.      172800  IN      A       184.170.255.201
a.ns.hosthaus.com.      172800  IN      AAAA    2001:470:7a:2::201
b.ns.hosthaus.com.      172800  IN      A       184.170.255.200
b.ns.hosthaus.com.      172800  IN      AAAA    2001:470:7a:2::200

I did send email to networksolutions.com to add IPv6 glue  -   no answer.

I called to networksolutions.com they suggest to edit and move dns to networksolutions.com and then I'll able to add AAAA records.

So question is, if I'll move dns to networksolutions.com will domain name pass the test to Verify IPv6 glue at TLD?

[kasperd]

I tried resolving the AAAA record for electronicnyipv6.net manually going through the recursion, and I found no problems resolving every step of the way over IPv6. The glue is there. When did you last change something on the domain? Maybe you just need to wait for the DNS cache at HE to expire and then retry. Some of the records involved have a 48 hour TTL.

[InnaGrushevsky]

I tried resolving the AAAA record for electronicnyipv6.net manually going through the recursion, and I found no problems resolving every step of the way over IPv6. The glue is there. When did you last change something on the domain? Maybe you just need to wait for the DNS cache at HE to expire and then retry. Some of the records involved have a 48 hour TTL.

I'm waiting since May 2012.

Step    Description    Data
1    Edit your submitted domain to a substring if needed    
2    Completed: Displaying NS information    Done
   a.ns.hosthaus.com. 2001:470:7a:2::201
   b.ns.hosthaus.com. 2001:470:7a:2::200

3. The authoritative namservers for your domain are out-of-bailiwick(glueless).
Please email at ipv6@he.net for further verification

[snarked]

Moving the DNS service has nothing to do with glue records at the registrar.  You got bad advice.  Try them again.

[kasperd]

3. The authoritative namservers for your domain are out-of-bailiwick(glueless).
Please email at ipv6@he.net for further verification

Did you try to email ipv6@he.net as the instruction says? The message doesn't actually say there is something wrong with your DNS records. Sounds like your configuration is a bit unusual, and the validation of such domains just hasn't been automated.

[InnaGrushevsky]

Answer from HE,

Thanks for your participation in our IPv6 certification program.

The whole basis for the Sage level of the IPv6 certification program is
for you to get glue in the gTLD for your authoritative nameservers
(using in-bailiwick). This is a necessary and important lesson for you
to go through. Not doing this step leaves out something that is a
standard operational task you are likely to be faced with in a real
world IPv6 implementation environment.

Here's what I suggest you to do.
Please create/add your own in-bailiwick NS, request the glue record via
your domain registrar and complete the Sage test.

-

Adding IPv6 glue at the registrar (Network Solutions) is a completely
separate matter from hosting your DNS there. You should just be able to
have Network Solutions add the glue records and that's it. I believe
this page has some instructions on adding glue records for Network
Solutions:
http://www.webhostingbuzz.com/wiki/reseller-hosting/how-add-glue-records/

If you have any concerns or questions, please feel free to ask.

Regards,

++++++++++++++++++++++++++

If I'll move DNS to networksolutions.com then it will not point to my hosting company.

Step #2 will fail:

2    Completed: Displaying NS information    Done
   a.ns.hosthaus.com. 2001:470:7a:2::201
   b.ns.hosthaus.com. 2001:470:7a:2::200

Thanks,

Inna