diff options
| author | Stefan Lindblom <StefanLindblom@users.noreply.github.com> | 2021-04-12 14:32:09 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-04-12 14:32:09 +0200 |
| commit | 5e61b6a7503af49735e73712c05c66eb1c531f93 (patch) | |
| tree | ada4c704a64bba4696fac6d5a6a7169fa131411d | |
| parent | e6bc0311ea254901b9239a3fc5c3e84f8b264cab (diff) | |
| download | vyos-documentation-5e61b6a7503af49735e73712c05c66eb1c531f93.tar.gz vyos-documentation-5e61b6a7503af49735e73712c05c66eb1c531f93.zip | |
Add information about specific VRF routing
As this thread states:
https://forum.vyos.io/t/system-name-server-vrf-aware/6710
There is no way to force system DNS traffic via a specific VRF, which is a pretty common scenario.
For example one could expect that all system services like DNS, auth, syslog, NTP, etc would use the management VRF (as specified by the user).
| -rw-r--r-- | docs/configuration/system/name-server.rst | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/configuration/system/name-server.rst b/docs/configuration/system/name-server.rst index 1896eeda..c105c712 100644 --- a/docs/configuration/system/name-server.rst +++ b/docs/configuration/system/name-server.rst @@ -4,6 +4,8 @@ System DNS ########## +.. warning:: If you are configuring a VRF for management purposes, there is + currently no way to force system DNS traffic via a specific VRF. This section describes configuring DNS on the system, namely: |