-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
VRF Enablement #28840
Comments
I cannot parse this. Any client can talk to resolved, it just answers universal truths about IP addresses/names. Or do you want per-VRF DNS zones with different dns servers? |
To be clear - i dont have a strong opinion or idea right now what the correct solution might be. Potentially systemd-resolved has no role to play. Simply raising this. |
For example, when all your network connections are in different VRFs (a very typical configuration on an ISP core router):
and resolved correctly reads the DNS config from networkd: (
A user would expect local DNS resolution to be working inside the VRF but not in main; but in reality, DNS resolution works in main but not in VRF.
This is caused by Linux do try to workaround this issue by using a PBR rule to redirect all local traffic to the local routing table:
But Here I'd like to propose 2 changes to make
|
Component
systemd-resolved
Is your feature request related to a problem? Please describe
When enabling VRFs DNS resolution will only work on the default VRF with systemd-resolved enabled
Describe the solution you'd like
I'm not sure what the correct solution is here, this bug is to document the limitation of systemd-resolved. Davind Ahern has a great writeup on it - https://people.kernel.org/dsahern/management-vrf-and-dns
Describe alternatives you've considered
Disable systemd-resolved, and just point /etc/resolv.conf to upstream
Leave systemd-resolved enabled, only having DNS resolution on the default VRF
The systemd version you checked that didn't have the feature you are asking for
249.11
The text was updated successfully, but these errors were encountered: