-
Notifications
You must be signed in to change notification settings - Fork 561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 nameservers #895
Labels
bug
Something isn't working
Comments
Thanks, I'll look into it. |
ghost
mentioned this issue
Jan 9, 2018
@reinerh @netblue30 Is this still relevant/reproducable or can this be closed? |
I would say that's still relevant. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
this is not a bug report, just some information about an issue Aidan Gauland reported on the Debian bugtracker.
He was using a firejail sandbox with --net=eth0 and was losing internet connectivity inside the sandbox (but not outside).
We figured out hostname resolution suddenly stopped working. He is using rdnssd on the host, which is a tool that autodiscovers IPv6 nameservers. This was overwriting the resolv.conf with a nameserver detected on the local network.
The content looked like this:
nameserver fe80::c6e9:84ff:1234:abcd%eth0
But as there was no eth0 interface inside the sandbox (instead there is a eth0-nnnnn interface), the nameserver was no longer reachable.
He also suggests to document this behavior on the known issues page.
The text was updated successfully, but these errors were encountered: