You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, I am not sure how this is any wanted behavior: it was rather done to work around a bug.
IMHO this just a misunderstanding, how binding link-local IPv6 addresses work. Typically you just need to provide a scope, which is actually given by the interface. This means that the semantics would be fully defined when using e.g. bind eth0
The problem is that this would require some more rewriting as the net.ParseIP does not support the scope (see e.g. ooni/probe#2036 here) . So I was just wondering before submitting a pull request if for whatever reason the link-local exception is wanted behaviour.
Why is this needed:
To me this is a real problem at the moment, when trying to use CoreDNS for local DNS rewriting. The problem with using a global address is that in my dynamic DNS setting the prefix may change, so I cannot hardcode the DNS Server for my network.
Feedback and workarounds welcome
The text was updated successfully, but these errors were encountered:
What would you like to be added:
#4531 removed linking link-local addresses altogether.
However, I am not sure how this is any wanted behavior: it was rather done to work around a bug.
IMHO this just a misunderstanding, how binding link-local IPv6 addresses work. Typically you just need to provide a scope, which is actually given by the interface. This means that the semantics would be fully defined when using e.g.
bind eth0
See eg. https://stackoverflow.com/questions/2460841/how-to-bind-a-link-local-address-to-an-ipv6-socket.
The problem is that this would require some more rewriting as the net.ParseIP does not support the scope (see e.g. ooni/probe#2036 here) . So I was just wondering before submitting a pull request if for whatever reason the link-local exception is wanted behaviour.
Why is this needed:
To me this is a real problem at the moment, when trying to use CoreDNS for local DNS rewriting. The problem with using a global address is that in my dynamic DNS setting the prefix may change, so I cannot hardcode the DNS Server for my network.
Feedback and workarounds welcome
The text was updated successfully, but these errors were encountered: