summaryrefslogtreecommitdiff
path: root/docs/automation/cloud-init.rst
diff options
context:
space:
mode:
authorStefan Lindblom <StefanLindblom@users.noreply.github.com>2021-04-12 14:32:09 +0200
committerGitHub <noreply@github.com>2021-04-12 14:32:09 +0200
commit5e61b6a7503af49735e73712c05c66eb1c531f93 (patch)
treeada4c704a64bba4696fac6d5a6a7169fa131411d /docs/automation/cloud-init.rst
parente6bc0311ea254901b9239a3fc5c3e84f8b264cab (diff)
downloadvyos-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).
Diffstat (limited to 'docs/automation/cloud-init.rst')
0 files changed, 0 insertions, 0 deletions