Not accepting AAAA is just about as bad as not accepting A records. You wouldn't certify a registrar if they couldn't update A records. It's about time certification was lost for failure to handle AAAA records. The same should also apply for DS records. In message <6D7961E1-F0FE-4674-8F8E-49CB5226DC35@hopcount.ca>, Joe Abley writes :
You have a choice of registrars. If you don't like the one you are using rig= ht now, choose a different one. There are lots to choose from.
http://www.icann.org/registrar-reports/accredited-list.html
Joe
Sent from my Ono-Sendai Cyberspace 7
On 2013-04-10, at 2:42, Alejandro Acosta <alejandroacostaalamo@gmail.com> wr= ote:
Hi Carlos, list, Today I entered to networksolutions.com and I remembered this thread. I had to administer a domain name and I sadly found they have done nothing in IPv6 during the last 12 month. =20 Regards, =20 ^Ao$ =20 On 3/28/12, Carlos Martinez-Cagnazzo <carlosm3011@gmail.com> wrote:
Hello all, =20 I just received a heads-up from a friend telling me that Network Solutions is unable/unwilling to configure AAAA's for .com/.net domains. He works for a large media outlet who will be enabling IPv6 on their sites for World IPv6 Launch Day. =20 I hope it's just a misunderstanding. If it's not, I would love to know if there is a reason for this, and if they have a timeline for supporting AAAA's. =20 It's ok to contact me privately. =20 regards =20 Carlos =20 -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org