[GH-ISSUE #629] Bug: Dual-Stack container listens only on IPv4 #208

New issue

Closed

opened 2026-02-26 04:34:24 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 04:34:24 +03:00

Owner

Originally created by @justarandomgeek on GitHub (Aug 16, 2025).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/629

What is Happening

A dual-stack container with both ipv4 and ipv6 addresses is only responding to dns requests on the container's ipv4 address. Some of my network service containers (including this dns proxy) run in a macvlan network bridged directly to my regular lan to handle various things colliding on fixed port numbers and/or providing L2-level services. This network has both ipv4 and ipv6 configured. The container is pingable (by an external host or another macvlan on the host, not the host directly due to macvlan quirks) by both addresses, and the web interface works fine over both, but the dns only responds on v4.

What is Expected

Listen on [::]:53 by default to get all (v4 and v6) container addresses

services:
 dns-proxy-server:
    image: defreitas/dns-proxy-server:latest
    hostname: dns.mageddo
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      host_vlan:
        ipv4_address: 192.0.2.253
        ipv6_address: 2001:db8::d0cc:11:0:fc1
networks:
  host_vlan:
    driver: macvlan
    driver_opts:
      parent: bond0
    enable_ipv6: true
    ipam:
      config:
        - subnet: 192.0.2.0/24
          gateway: 192.0.2.1
          ip_range: 192.0.2.252/30
        - subnet: 2001:db8::/64
          gateway: 2001:db8::1
          ip_range: 2001:db8::d0cc:11:0:fc0/122

(real network replaced with documentation prefixes)

Originally created by @justarandomgeek on GitHub (Aug 16, 2025). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/629 ## What is Happening A dual-stack container with both ipv4 and ipv6 addresses is only responding to dns requests on the container's ipv4 address. Some of my network service containers (including this dns proxy) run in a macvlan network bridged directly to my regular lan to handle various things colliding on fixed port numbers and/or providing L2-level services. This network has both ipv4 and ipv6 configured. The container is pingable (by an external host or another macvlan on the host, not the host directly due to macvlan quirks) by both addresses, and the web interface works fine over both, but the dns only responds on v4. ## What is Expected Listen on `[::]:53` by default to get all (v4 and v6) container addresses ``` services: dns-proxy-server: image: defreitas/dns-proxy-server:latest hostname: dns.mageddo volumes: - /var/run/docker.sock:/var/run/docker.sock networks: host_vlan: ipv4_address: 192.0.2.253 ipv6_address: 2001:db8::d0cc:11:0:fc1 networks: host_vlan: driver: macvlan driver_opts: parent: bond0 enable_ipv6: true ipam: config: - subnet: 192.0.2.0/24 gateway: 192.0.2.1 ip_range: 192.0.2.252/30 - subnet: 2001:db8::/64 gateway: 2001:db8::1 ip_range: 2001:db8::d0cc:11:0:fc0/122 ``` (real network replaced with documentation prefixes)

kerem closed this issue

2026-02-26 04:34:24 +03:00

kerem commented

2026-02-26 04:34:24 +03:00

Author

Owner

@justarandomgeek commented on GitHub (Nov 8, 2025):

So, is this project abandoned? this is a show-stopper level bug that has been ignored for like 4 months!

@justarandomgeek commented on GitHub (Nov 8, 2025): So, is this project abandoned? this is a show-stopper level bug that has been ignored for like 4 months!

kerem commented

2026-02-26 04:34:24 +03:00

Author

Owner

@mageddo commented on GitHub (Dec 17, 2025):

Hey @justarandomgeek. I will analyse your issue between today and tomorrow.

It looks like you’re frustrated with how fast things are happening, and I totally understand that — but hey, I’m your friend.

This is an open-source project that I’ve been maintaining for almost 10 years as a contribution to the community. I work on it in my free time, and I don’t have any sponsorship to keep it running.

Despite that, things do get fixed eventually, and the project will keep moving forward.

This year, I worked on a huge refactoring of the project to fix a lot of issues that were causing the same kind of problems, and I finally got that done today.

@mageddo commented on GitHub (Dec 17, 2025): Hey @justarandomgeek. I will analyse your issue between today and tomorrow. It looks like you’re frustrated with how fast things are happening, and I totally understand that — but hey, I’m your friend. This is an open-source project that I’ve been maintaining for almost 10 years as a contribution to the community. I work on it in my free time, and I don’t have any sponsorship to keep it running. Despite that, things do get fixed eventually, and the project will keep moving forward. This year, I worked on a huge refactoring of the project to fix a lot of issues that were causing the same kind of problems, and I finally got that done today.

kerem commented

2026-02-26 04:34:24 +03:00

Author

Owner

@mageddo commented on GitHub (Dec 19, 2025):

Beta is out 5.5.1-snapshot, I would appreciate feedback. Thanks in advance.

dig -p 53 host.docker @2804:14c:213:5427::253 +noall +answer
host.docker.		30	IN	A	172.20.5.1

My test file

services:
  dns-proxy-server:
    image: defreitas/dns-proxy-server:5.5.1-snapshot
    hostname: dns.mageddo
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment: 
      DPS_LOG__LEVEL: DEBUG
    networks:
      host_vlan:
        ipv4_address: 192.168.0.253
        ipv6_address: 2804:14c:213:5427::253

  testapp:
    image: ubuntu:22.04
    command: sleep infinity
    networks:
      host_vlan:
        ipv4_address: 192.168.0.252
        ipv6_address: 2804:14c:213:5427::252
networks:
  host_vlan:
    driver: macvlan
    driver_opts:
      parent: eno1
    enable_ipv6: true
    ipam:
      config:
        - subnet: 192.168.0.0/24
          gateway: 192.168.0.1
          ip_range: 192.168.0.252/30
        - subnet: 2804:14c:213:5427::/64
          gateway: 2804:14c:213:5427::1
          ip_range: 2804:14c:213:5427::250/124

@mageddo commented on GitHub (Dec 19, 2025): Beta is out [5.5.1-snapshot][1], I would appreciate feedback. Thanks in advance. ```bash dig -p 53 host.docker @2804:14c:213:5427::253 +noall +answer host.docker. 30 IN A 172.20.5.1 ``` My test file ```yml services: dns-proxy-server: image: defreitas/dns-proxy-server:5.5.1-snapshot hostname: dns.mageddo volumes: - /var/run/docker.sock:/var/run/docker.sock environment: DPS_LOG__LEVEL: DEBUG networks: host_vlan: ipv4_address: 192.168.0.253 ipv6_address: 2804:14c:213:5427::253 testapp: image: ubuntu:22.04 command: sleep infinity networks: host_vlan: ipv4_address: 192.168.0.252 ipv6_address: 2804:14c:213:5427::252 networks: host_vlan: driver: macvlan driver_opts: parent: eno1 enable_ipv6: true ipam: config: - subnet: 192.168.0.0/24 gateway: 192.168.0.1 ip_range: 192.168.0.252/30 - subnet: 2804:14c:213:5427::/64 gateway: 2804:14c:213:5427::1 ip_range: 2804:14c:213:5427::250/124 ``` [1]: https://github.com/mageddo/dns-proxy-server/releases/tag/5.5.1-snapshot

kerem commented

2026-02-26 04:34:24 +03:00

Author

Owner

@mageddo commented on GitHub (Dec 19, 2025):

Since 5.6.x, you will have to set server.host to :: to enable ipv6 listening. see #607

@mageddo commented on GitHub (Dec 19, 2025): Since 5.6.x, you will have to set `server.host` to `::` to enable ipv6 listening. see #607