vyos-documentation.git/docs/configuration/system/name-server.rst, branch 1.4.3VyOS readthedocs (mirror of https://github.com/vyos/vyos-documentation.git)
https://git.amelek.net/vyos/vyos-documentation.git/atom?h=1.4.32023-12-30T09:45:27+00:00system: T5877: Shorten system domain-search config path2023-12-30T09:45:27+00:00Christian Breunigchristian@breunig.cc2023-12-30T09:44:58+00:00urn:sha1:20a6836e167260616d6f0e8868e135b71e5f8fc0
Documentation pdate for https://github.com/vyos/vyos-1x/pull/2718
(cherry picked from commit 05215848a5df37a4cc4075a58b05f19871a56306)
autosectionlabel: add custom headline ref2021-06-11T20:19:55+00:00rebortggithub@ghlr.de2021-06-11T20:19:55+00:00urn:sha1:df504dd6c16277b305757fe4500e05b81c150da0Add information about specific VRF routing2021-04-12T12:32:09+00:00Stefan LindblomStefanLindblom@users.noreply.github.com2021-04-12T12:32:09+00:00urn:sha1:5e61b6a7503af49735e73712c05c66eb1c531f93
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).system: fix lint errors2020-12-11T14:08:50+00:00rebortggithub@ghlr.de2020-12-11T14:08:50+00:00urn:sha1:4f5320bd55e6659be51a2d15b6df348b5d112937arrange: system configration2020-11-30T20:15:16+00:00rebortggithub@ghlr.de2020-11-30T20:15:16+00:00urn:sha1:b1cb71c71935ad6b0a7d9effe8f4dc4467de2175