Ticket #364 (closed defect: invalid)

Opened 2 years ago

Last modified 2 years ago

Binding to IPv6 ::0 --> error: Fatal error: Unable to bind to UDP ipv6 socket

Reported by: anon Owned by: somebody
Priority: normal Milestone:
Component: component1 Version:
Severity: normal Keywords:
Cc:

Description

When trying to bind to ::0 IPv6 address with config like this:

local-address=0.0.0.0
local-ipv6=::0

one will get an error:

Jun  1 15:24:28 vr4 pdns[26942]: binding to UDP ipv6 socket: Address already in use
Jun  1 15:24:28 vr4 pdns[26942]: Fatal error: Unable to bind to UDP ipv6 socket

Through when you explicitly specify an IPv6 address everything works well.

More info about this bug can be found here:  https://blog.misc.ephaone.org/archives/powerdns_postfix_ipv6.html

The workaround (from the link above) is to use the following config

local-address=
local-ipv6=::0

Attachments

patch Download (1.7 KB) - added by anon 2 years ago.
Patch that fixes this porblem

Change History

follow-up: ↓ 2   Changed 2 years ago by ahu

  • status changed from new to closed
  • resolution set to invalid

You got your workaround right there ;-) I'm afraid you've discovered exactly how things should work..

Changed 2 years ago by anon

Patch that fixes this porblem

in reply to: ↑ 1   Changed 2 years ago by anon

Replying to ahu:

You got your workaround right there ;-) I'm afraid you've discovered exactly how things should work..

Not exactly.

1. If I use workaround, it replaces all IPv4 addresses with IPv6 ::ffff:127.0.0.1 instead of 127.0.0.1 for example. This confuses per-host-axfr-acl patch:  http://wiki.powerdns.com/trac/changeset/1360

2. This issue should be cleared in conf file and in documentation, if this is expected behavior. It took me some time to find this workaround... And it did not helped me as it is said in (1). Patch, I've created -- helped, but I am not sure it would be useful for everyone.

Note: See TracTickets for help on using tickets.