<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I feel your pain, Michael. I'm a GoDaddy customer, but only because they were "the thing" back when I registered. </div><div><br></div><div>Leo Laporte used to advertise for them, but got fed up with the ads and the "do you want fries with that" checkout process.</div><div><br></div><div>He's pimpin' <a href="http://hover.com">hover.com</a> right now. It looks a lot simpler and easier, but I can't speak for their tech. My *understanding* is that they're better, but be your own best judge. They're the old TuCows people, so at least they've been around the block. I'd hope they've got a CCIE or two on the payroll that can properly answer your question.</div><div><br></div><div>Just a suggestion. I have no direct knowledge.</div><div><br></div><div>--j</div><div><br></div><br><div><div>On Jan 22, 2011, at 8:52 PM, Michael B. Trausch wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div>
On Sat, 2011-01-22 at 18:02 -0500, Chuck Peters wrote:<br>
<blockquote type="CITE">
I am interested in what you find out. I think at least a few others on the list will be as well.<br>
</blockquote>
<br>
This is one of those emails that I am writing in HTML because of its inherent expressiveness. I apologize in advance if that is annoying to anyone. I suppose it probably does not matter much, though, since it appears that my phone sends HTML mail by default anyway. Grr.<br>
<br>
I submitted a ticket to them on their Domain Manager product, with the following text:<br>
<br>
<blockquote type="CITE">
The GoDaddy Domain Manager is not providing me with the ability to add IPv6 glue records to my <a href="http://trausch.us">trausch.us</a> domain. This seems to be an arbitrary restriction, since the .us TLD supports IPv6 now. What is the procedure that is required to add IPv6 glue? I need to get my nameservers listed with their IPv6 addresses such that they are able to be found on the IPv6 Internet. Thanks!<br>
</blockquote>
<br>
This was met with the following response (go ahead, laugh; I would if I were you):<br>
<br>
<blockquote type="CITE">
<table cellspacing="1" cellpadding="2" width="100%">
<tbody><tr>
<td bgcolor="#99cc99">
<b>Support Staff Response</b>
</td>
</tr>
<tr>
<td>
Dear Michael Trausch,<br>
Thank you for contacting online support.<br>
<br>
<b>AAAA</b> — AAAA records store a 128-bit Internet Protocol version 6 (IPv6) address that does not fit the standard A record format. For example, 2007:0db6:85a3:0000:0000:6a2e:0371:7234 is a valid 128-bit/IPv6 address.<br>
<br>
It maps the host name to an address associated with a domain name and specifies that AAAA records must be processed.<br>
<br>
<h4>
<b>To Add an AAAA Record</b>
</h4>
<ol type="1">
<br>
<li type="1" value="1">Go to the Zone File Editor for the domain name you want to update.
</li><li type="1" value="2">Click <b>Add New Record</b>. The Add DNS Record window displays.
</li><li type="1" value="3">From the <b>Record type</b> list, select <b>AAAA</b>.
</li><li type="1" value="4">Complete the following fields:
<ul>
<br>
<li><b>Host Name</b> — Enter the host name or domain name that links to this AAAA record.
</li><li><b>Points to IPv6 Address</b> — Enter the 128-bit address.
</li><li><b>TTL</b> — Select how long the server should cache the information.
</li></ul>
<br>
</li><li type="1" value="5">Click <b>OK</b>.
</li><li type="1" value="6">Click <b>Save Zone File</b>, and then click <b>OK</b>. The AAAA record displays in the AAAA (IPv6) section.
</li></ol>
<h4>
<b>To Edit an AAAA Record</b>
</h4>
<ol type="1">
<br>
<li type="1" value="1">Go to the Zone File Editor for the domain name you want to update.
</li><li type="1" value="2">In the <b>AAAA (IPv6)</b> section, click the AAAA record you want to edit.
</li><li type="1" value="3">Edit any of the following fields:
<ul>
<br>
<li><b>Host</b> — Enter the host name or domain name that links to this AAAA record.
</li><li><b>Points to</b> — Enter the 128-bit address.
</li><li><b>TTL</b> — Select how long the server should cache the information.
</li></ul>
<br>
</li><li type="1" value="4">Click <b>Save Zone File</b>, and then click <b>OK</b>.
</li></ol>
<br>
Please let us know if we can help you in any other way.<br>
Sincerely,<br>
S Roberts<br>
Customer Care
</td>
</tr>
</tbody></table>
</blockquote>
<br>
Before I even start to nit-pick about the contents of that text, <b><i>it is completely not what I asked for!</i></b> I asked them for the ability to add glue records to my domains in the .us TLD. I did not ask them for how to add AAAA records to my DNS. Had they taken thirty seconds to both read my request and see that I do not use their bundled DNS hosting solution, I think even a five year old who had some knowledge of this problem domain would have seen that this reply was completely irrelevant. It is something that frankly I would expect from an automated system, not a human being that is support to be supporting the domain registrar's operation. Oh, and the example address they used is incorrect; <a href="http://tools.ietf.org/html/rfc3849">RFC 3849</a> clearly states that the reserved example address is 2001:db8::/32. Sigh.<br>
<br>
So, naturally, I replied back and asked them to re-read my original request, because they did not answer it. They then replied with this:<br>
<br>
<blockquote type="CITE">
<table cellspacing="1" cellpadding="2" width="100%">
<tbody><tr>
<td bgcolor="#99cc99">
<b>Support Staff Response</b>
</td>
</tr>
<tr>
<td>
Michael,<br>
<br>
The .Us registry restrict you from adding this. The .Com registry allows it. <br>
So to clarify, it is the .Us registry that does not allow you to do this.<br>
<br>
Regards,<br>
Cole<br>
ONline support
</td>
</tr>
</tbody></table>
</blockquote>
<br>
<sarcasm>Oh, most excellent. The blame game! I almost thought that corporations stopped playing that game, I hadn't encountered it in a while.</sarcasm> At this point, I'm downright <i>pissed</i> because I know better, and boy do I hate being lied to. Even more than hating being lied to, I hate it when someone <b>who is paid to provide support</b> disseminates information that they could not have possibly confirmed before sending, because it is so clearly incorrect.<br>
<br>
My reply to this was <i>quite</i> lengthy. If anyone is interested in seeing its full text, I'll happily send that (in fact, I am seriously considering posting this whole clusterfuck to the Web somewhere). Anyway, in it, I basically said that the .us TLD does in fact support IPv6 glue: they have nameservers on the IPv6 network, and those name servers have and return AAAA glue records for nameservers listed in the .us TLD. I included the list of nameservers and their addresses, and output from ping6 showing that they are indeed reachable. Then I downloaded the .us TLD zone file so that I could identify the 35 AAAA glue records in the .us domain. I found those, and found that there are indeed 35 such glue records, and they belong to a total of 17 domains.<br>
<br>
So, I included data for one such domain, <a href="http://4LL.US">4LL.US</a>, and pasted the output of <tt>dig -t any <a href="http://4LL.US">4LL.US</a> @J.CCTLD.US</tt> showing that indeed there are glue records present. Then pulled up all the information for the 17 domains that have glue records, and I found that majority of them had their glue records created while they were at <a href="http://gkg.net">gkg.net</a> (IANA ID #93). One of those domains was transferred to GoDaddy, though they came from <a href="http://gkg.net">gkg.net</a> and apparently their glue also transferred. Well, isn't that nice. I guess I can have IPv6 glue at GoDaddy, just have to transfer my domain elsewhere, add it, and transfer it back, right? Too much bloody work.<br>
<br>
In response to the long mail I sent them, which contained proof that .us TLD accepts glue, and pointers to two domain registrars that support it (<a href="http://gkg.net">gkg.net</a> and <a href="http://gandi.net">gandi.net</a>), <b>and</b> included all the information required for them to independently validate the proof, they sent this in reply:<br>
<br>
<blockquote type="CITE">
The .Us registry restricts you from adding this. The .Com registry allows it. <br>
So to clarify, it is the .Us registry that does not allow you to do this.<br>
<br>
If you had any other additional questions or concerns, please feel free to let us know.<br>
If you were in need of immediate assistance please contact our Customer Care Dept. @ 1-404-505-8877, they are available 24/7 - 365.<br>
<br>
Thank You.<br>
Josh S.<br>
Sales/Support<br>
</blockquote>
<br>
Wait, what‽<br>
<br>
What an excellent copy and paste! I am guessing that was their way of saying "TL;DR".<br>
<br>
At this point, I am ready to leave and transfer all my stuff from GoDaddy to another registrar (looks like <a href="http://gkg.net">gkg.net</a> and <a href="http://gandi.net">gandi.net</a> are my two choices, though there could be more that I am unaware of: I'd be interested in anyone who is at a registrar other than those two that support .us IPv6 glue as well as the others like .com, .net, .cc, .org…). Erica, however, says, "Try one more thing. They have <a href="http://twitter.com/godaddy">a Twitter account</a>, see if that yields a result." So, I <a href="http://twitter.com/mtrausch/status/28936549026500608">attempted just that</a>. They asked for my phone number, I sent that to them over a private channel, and they called me about 3 hours later.<br>
<br>
So, talking to the poor schmuck who called me winds up with this bullet point summary:
<ul>
<li>They can submit the issue to their development team, but they cannot provide any sort of status. Apparently their development team and its manager are completely and totally inaccessible to their support team (either that is a lie, or they are horrendously inefficient internally).
</li><li>He has seen them implement things within a month in the past, but honestly expects that to be the absolute minimum. (Why? If this is more than a simple change in a database table, they are doing it completely wrong and in a manner which cannot possibly hope to eventually scale to all domain types).
</li><li>Customers are absolutely not allowed to get in touch with anyone but support.
</li><li>Support is not allowed to look at the issue tracking system that the developers use, so they cannot provide any status at any point.
</li><li>When asked "will you keep me in the loop," he said "I have no way to do that. To see when it is fixed, keep checking the site."
</li><li>When asked "can I reasonably expect this in 2 to 6 weeks?" he said, "probably, but I honestly don't know."
</li></ul>
Points to the man who called me for at least knowing that it's perfectly okay to say "I don't know," but by this point I see no hope. Here's where I stand at the moment:
<ul>
<li>GoDaddy does not support IPv6 glue in the .us TLD.
</li><li>GoDaddy does not seem to care that they should be supporting IPv6 glue for all the TLDs they provide domain name sales for.
</li><li>GoDaddy doesn't seem to be clueful at all about what IPv6 is, or why they should give a rat's ass about it.
</li><li>GoDaddy won't provide an estimate as to when I will be able to add IPv6 glue. "Could be 1 month, could be 6," exact quote.
</li><li>GoDaddy won't give its customers anything approaching service until they threaten to leave. Wish I could say that I'm shocked or surprised or something, but that seems to be the norm across all bloody businesses in this day and age. No company seems to care to keep their customers happy. They just work to keep their customers from being furious, that's all. Two very different things.
</li><li>At least <a href="http://gkg.net">gkg.net</a> and <a href="http://gandi.net">gandi.net</a> provide the service I want, but I don't know if they provide IPv6 glue universally or just for select domains.
</li><li><a href="http://gandi.net">gandi.net</a> appears to be more expensive than <a href="http://gkg.net">gkg.net</a>. But I like their tag line, which is "no bullshit." That said, I don't believe their tagline. I just think it's cool.
</li></ul>
So, that's where I stand. That's where GoDaddy stands.<br>
<br>
I wish I could say that I had faith that out there, somewhere, is a business that knows what it is doing and takes pride in the quality of its support. But honestly, I can't even trust my own history with companies to provide insight as to the quality of their customer service.<br>
<br>
What a crazy, careless, fucked up world we live in.<br>
<br>
I withdraw my recommendation that anyone use GoDaddy.<br>
<br>
— Mike
</div>
_______________________________________________<br>Ale mailing list<br><a href="mailto:Ale@ale.org">Ale@ale.org</a><br><a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a><br>See JOBS, ANNOUNCE and SCHOOLS lists at<br>http://mail.ale.org/mailman/listinfo<br></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">#!/jerald<br>Linux User #183003</div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Ubuntu User #32648</div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Public GPG Key: <a href="http://questy.org/js.asc">http://questy.org/js.asc</a><br><br>-----BEGIN GEEK CODE BLOCK-----<br>Version: 3.1<br>GIT/MU d-@ s++(++)>+++:> a+ C++++(+++)$>++ UBLAVHSC++(on)$>++++ P++(+++)$>++++ L++(++++)$>+++ !E---(---)>--- W+(++)$>+++ N(+)$>++ !o !K-- w(--)>--- O()@> M++(++)$>++ V()>- PS+++()@>-- PE(++)@>+ Y+(+)@>+ PGP++(++)$>+++ t+(++)@>+++ 5(+)@>+ X+(++)@>+++ R+(+)@>++ tv-(+)$>++ b+++(++)$>++ DI++++(++)>+++ D++(++)@>++ G++(++)@>++ e++(++)$>++ h(-)$>- r+++(+++)@>+++ y+(+++)>++++@ <br>------END GEEK CODE BLOCK------<br><br><br></div></span></div></span></span>
</div>
<br></body></html>