# IPv6 hostname broken?

**URL:** <https://discussions.flightaware.com/t/ipv6-hostname-broken/95601>\
**Category:** ADS-B Flight Tracking\
**Created:** [October 2, 2024, 3:31pm UTC](https://discussions.flightaware.com/t/ipv6-hostname-broken/95601 "2024-10-02T15:31:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![downwindz](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/downwindz/32/124556_2.png) [@downwindz](https://discussions.flightaware.com/u/downwindz)\
**Post date:** [October 2, 2024, 3:31pm UTC](https://discussions.flightaware.com/t/ipv6-hostname-broken/95601/1 "2024-10-02T15:31:20Z")

</div>

Using the ipv6 host name for feeding but having some issues.

[piaware-ipv6.flightaware.com](http://piaware-ipv6.flightaware.com) resolves as five hosts under the 2620:13d:c000:11:: network, but none of them work for connecting on port 1200.

[piaware.flightaware.com](http://piaware.flightaware.com) also has these same five non working hosts listed (and an extra on the same network), but also a bunch under 2620:13d:c004:11::\* which _do_ work.

Is this an intentional change of some sort or just a temporary issue? Got a notification that my piaware wasn’t feeding and this turned out to be the issue, dunno if I need to work around it or just wait for things to stabilize on the FlightAware side 🙂

---

<div class="post-metadata">

**Author:** ![mduell](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mduell/32/115680_2.png) [@mduell](https://discussions.flightaware.com/u/mduell)\
**Post date:** [October 2, 2024, 5:15pm UTC](https://discussions.flightaware.com/t/ipv6-hostname-broken/95601/2 "2024-10-02T17:15:41Z")

</div>

Thanks for the report, fixing.

---

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [October 3, 2024, 2:58am UTC](https://discussions.flightaware.com/t/ipv6-hostname-broken/95601/3 "2024-10-03T02:58:53Z")

</div>

We’ve updated the piaware-ipv6 name to include the same v6 addresses as in the piaware name.

The :c000: addresses are still broken – continuing to look into that one.

Note that there’s _usually_ no reason to use [piaware-ipv6.flightaware.com](http://piaware-ipv6.flightaware.com) instead of the default [piaware.flightaware.com](http://piaware.flightaware.com), unless you have unusual requirements to entirely avoid even trying the v4 addresses that can’t be handled by local configuration (e.g. gai.conf)

---

<div class="post-metadata">

**Author:** ![downwindz](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/downwindz/32/124556_2.png) [@downwindz](https://discussions.flightaware.com/u/downwindz)\
**Post date:** [October 3, 2024, 5:01am UTC](https://discussions.flightaware.com/t/ipv6-hostname-broken/95601/4 "2024-10-03T05:01:53Z")

</div>

Thanks for the fix! 🙂

As to why I use the ipv6 name, “it’s complicated”. I run everything in docker and it seems to do some “magic” networking wise that makes the container prefer ipv4 (something about using local addresses for the docker network and doing ipv6 nat to the Internet so gai.conf doesn’t prefer ipv6 on that address type). I can probably figure out how to patch gai.conf inside the container to fix it but it was easier to just use the dedicated ipv6 hostname and give it no “wrong options” 🙂

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/system/32/38558_2.png) [@system](https://discussions.flightaware.com/u/system)\
**Post date:** [October 3, 2025, 5:02am UTC](https://discussions.flightaware.com/t/ipv6-hostname-broken/95601/5 "2025-10-03T05:02:04Z")

</div>

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.