Magic DNS and AAAA records pointing at IPv6 addresses of nodes in dual-stack tailnet #384

Closed
opened 2025-12-29 01:28:00 +01:00 by adam · 2 comments
Owner

Originally created by @almereyda on GitHub (Nov 29, 2022).

Issue description

When connecting to a dual stack tailnet, only A records of nodes are resolved via Magic DNS.

To Reproduce

  1. dig +short A node1.ns.headscale.fqdn
  2. dig +short AAAA node1.ns.headscale.fqdn

Context info

This sounds as if it is related to:

The nodes list also only displays the IPv6 address in the first column.

It is possible to ping the displayed IPv6 address, and it is possible to retrieve the IPv4 address via Magic DNS.

Ideally, both of these functionalities (display + DNS) could support dual stack mode more completely.

  • Version of headscale used: latest
  • Version of tailscale client: 1.32.3
  • Linux Ubuntu 22.04
  • Kernel 5.15.0-53-generic
Originally created by @almereyda on GitHub (Nov 29, 2022). **Issue description** When connecting to a dual stack tailnet, only A records of nodes are resolved via Magic DNS. **To Reproduce** 1. `dig +short A node1.ns.headscale.fqdn` 2. `dig +short AAAA node1.ns.headscale.fqdn` **Context info** This sounds as if it is related to: - #295 The nodes list also only displays the IPv6 address in the first column. It is possible to ping the displayed IPv6 address, and it is possible to retrieve the IPv4 address via Magic DNS. Ideally, both of these functionalities (display + DNS) could support dual stack mode more completely. - Version of headscale used: `latest` - Version of tailscale client: `1.32.3` - Linux Ubuntu 22.04 - Kernel 5.15.0-53-generic
adam added the bug label 2025-12-29 01:28:00 +01:00
adam closed this issue 2025-12-29 01:28:00 +01:00
Author
Owner

@juanfont commented on GitHub (Nov 30, 2022):

I am afraid we depend on upstream for this one. Please have a look to https://github.com/tailscale/tailscale/issues/1152

@juanfont commented on GitHub (Nov 30, 2022): I am afraid we depend on upstream for this one. Please have a look to https://github.com/tailscale/tailscale/issues/1152
Author
Owner

@almereyda commented on GitHub (Dec 2, 2022):

Pardon me for not finding that, and thanks for the link.

On Wed, 30 Nov 2022 at 00:01, Juan Font @.***> wrote:

Closed #1027 https://github.com/juanfont/headscale/issues/1027 as
completed.


Reply to this email directly, view it on GitHub
https://github.com/juanfont/headscale/issues/1027#event-7917167452, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMRV7AA5IYU5355O56674TWK2DLBANCNFSM6AAAAAASOB5SCQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

@almereyda commented on GitHub (Dec 2, 2022): Pardon me for not finding that, and thanks for the link. On Wed, 30 Nov 2022 at 00:01, Juan Font ***@***.***> wrote: > Closed #1027 <https://github.com/juanfont/headscale/issues/1027> as > completed. > > — > Reply to this email directly, view it on GitHub > <https://github.com/juanfont/headscale/issues/1027#event-7917167452>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAMRV7AA5IYU5355O56674TWK2DLBANCNFSM6AAAAAASOB5SCQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#384