AAAA ::1 <--- someone from Aruba who can fix that?

Hi folks,

For quite a few folks here on the list travel is a common thing, going
into foreign wireless networks is too. Likely your laptop/tablet comes
with IPv6 enabled per default, it is 2012 after all almost going 2013.

And then you get to a silly hotspot and it does not work as the
connection fails (or you get the website you host on your laptop and go
'huh?' ;).

Thus you check and you see:
$ dig aaaa

; <<>> DiG 9.8.3-P1 <<>> aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25608
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0



;; Query time: 19 msec
;; WHEN: Tue Dec 4 10:12:33 2012
;; MSG SIZE rcvd: 75

I am fairly sure somebody technical and high enough up at Aruba knows
how to get this resolved, sooner or later... thus please do, it will
start hurting more and more people every day.

Oh, and btw, it has an A record too, but even though Happy Eyeballs
exists in a magical form inside OSX, ::1 is a very close route thus will
always win over the IPv4 address.

Of course, temp disabling IPv6 on the link is a way to circumvent it,
but heck, why is that DNS server publishing ::1 at all!?


This whole DNS hack is broken, browsers will cache the record and
you end up with breakage when using different captive portals in
succession. The hostname used should at least be different for each

Other aruba dns hacks, like, are even more
painful; it is rather annoying when you know the address of a device, try to
access it and it keeps redirecting you to a faked DNS name that does not