It is the response I received from he.net support :
---------------------------------------------------------------------------
Hi,
Thanks for your participation in our IPv6 Certification Program.
In Sage level, we check to see if your domain's authoritative NS have
IPv6 glue with their listed TLD servers.
We use the following methods to check IPv6 glue:
1. dig +trace ns $domain to get the TLD server list
2. dig aaaa $ns @TLD for the glue
I've manually checked your domain's authoritative NS and did not see
IPv6 glue with their listed TLD server.
See the following result:
:~$ dig NS
www.bbvps.com +trace
; <<>> DiG 9.4.2-P2.1 <<>> NS
www.bbvps.com +trace
;; global options: printcmd
. 54232 IN NS j.root-servers.net.
. 54232 IN NS b.root-servers.net.
. 54232 IN NS f.root-servers.net.
. 54232 IN NS g.root-servers.net.
. 54232 IN NS e.root-servers.net.
. 54232 IN NS k.root-servers.net.
. 54232 IN NS l.root-servers.net.
. 54232 IN NS i.root-servers.net.
. 54232 IN NS c.root-servers.net.
. 54232 IN NS m.root-servers.net.
. 54232 IN NS a.root-servers.net.
. 54232 IN NS d.root-servers.net.
. 54232 IN NS h.root-servers.net.
;; Received 497 bytes from 127.0.0.1#53(127.0.0.1) in 33 ms
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 494 bytes from 2001:500:1::803f:235#53(h.root-servers.net)
in 67 ms
bbvps.com. 172800 IN NS ns1.bbvps.com.
bbvps.com. 172800 IN NS ns2.bbvps.com.
bbvps.com. 172800 IN NS ns201.bbvpsdns.com.
bbvps.com. 172800 IN NS ns4.bbvps.com.
bbvps.com. 172800 IN NS ns5.bbvps.com.
;; Received 224 bytes from 192.35.51.30#53(f.gtld-servers.net) in 14 ms
www.bbvps.com. 3600 IN CNAME bbvps.com.
bbvps.com. 3600 IN NS ns2.bbvps.com.
bbvps.com. 3600 IN NS ns1.bbvps.com.
bbvps.com. 3600 IN NS ns201.bbvpsdns.com.
bbvps.com. 3600 IN NS ns4.bbvps.com.
bbvps.com. 3600 IN NS ns5.bbvps.com.
;; Received 238 bytes from 204.42.254.5#53(ns4.bbvps.com) in 51 ms
:~$ dig NS com | grep AAAA
a.gtld-servers.net. 64204 IN AAAA 2001:503:a83e::2:30
:~$ dig AAAA ns2.bbvps.com @2001:503:a83e::2:30 +short
<No Answer>
:~$ dig AAAA ns1.bbvps.com @2001:503:a83e::2:30 +short
<No Answer>
:~$ dig AAAA ns201.bbvpsdns.com @2001:503:a83e::2:30 +short
<No Answer>
:~$ dig AAAA ns4.bbvps.com @2001:503:a83e::2:30 +short
<No Answer>
:~$ dig AAAA ns5.bbvps.com @2001:503:a83e::2:30 +short
<No Answer>
If you have questions, please let us know.
Regards,
Tae Kim
Hurricane Electric
AS6939
--------------------------------------------------------------------
but I dont think it is the correct method to check glue records , the correct method is :
bbvps:~# dig NS bbvps.com @a.gtld-servers.net | grep AAAA
ns201.bbvpsdns.com. 172800 IN AAAA 2001:470:1f06:25a::2
the method which he.net support has provided even doesnt work for their own domain :
bbvps:~# dig AAAA ns2.he.net @2001:503:a83e::2:30 +short
<No Answer>
the correct method is :
bbvps:~# dig NS he.net @a.gtld-servers.net | grep AAAA
ns2.he.net. 172800 IN AAAA 2001:470:200::2
ns3.he.net. 172800 IN AAAA 2001:470:300::2
ns4.he.net. 172800 IN AAAA 2001:470:400::2
ns5.he.net. 172800 IN AAAA 2001:470:500::2
and here you go , all glue records are set.