IPv6 source address #1384
Replies: 2 comments 3 replies
-
Some debugging: This, in turn, causes I found a few places which claim that
In any case, I found some pointers, that |
Beta Was this translation helpful? Give feedback.
-
Thanks for asking. The Source Address feature is used for outbound requests and thus is not related to the issue you have here. The issue is also not related to IPv6 and will come with IPv4 too with multiple interfaces on Linux servers. The issue is just that the DNS responses get routed out of the interface which has the default route on Linux. The fix is to configure the IP address on the additional interfaces with the "DNS Server Local End Points" option. Once the DNS server binds to those specific IP addresses, the responses will be returned via the correct interface. Let me know if that worked. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I recently changed my ISP and finally have a working native IPv6 connection, so I'm now reconfiguring my LAN to use IPv6 wherever possible. It is going fine, but DNS is causing me some headaches.
My Technitium DNS instance runs on a server which has multiple interfaces which are assigned
192.168.1.x and 2a02:XXXX:XXXX::x (redacted) where x = 2...10. The DNS server should respond on x = 10 (other services are bound to the other IPs).
When I test the DNS server logged in to the server over ssh (or the DNS Client feature on the web), it all seems fine:
However, from other machines on the LAN:
So it seems like, when using IPv6, the server chooses the wrong source address in its response, which are set to the defaults:
Changing the
DNS Server IPv6 Source address
alone doesn't change anything (as is documented).As soon as I set
DNS Server IPv6 Source address
to 2a02:XXXX:XXXX::10 and enablePrefer IPv6
, DNS resolution stops working and produces a lot of timeouts instead. For example:I noticed that in the above example, all name server were resolved the IPv4 instead of IPv6 addresses. I also have many examples of log entries which resulted in SERVFAIL responses (I think that's when I had also set the IPv4 source address list to just
192.168.1.10
):I think I'm probably misunderstanding the semantics of these configuration settings.
Could you please help me configuring Technitium DNS so that it can also serve as the DNS server for the LAN clients using IPv6 (in addition to IPv4)?
Beta Was this translation helpful? Give feedback.
All reactions