https://github.com/vyos/vyos-1x/commit/36f8a1e4e5966c43c5330ff223fa2ef07d346b6e

The same thing applies to the global configuration of push options.
E.g. These:
set interfaces openvpn vtun0 server push-route '172.16.41.0/24'
set interfaces openvpn vtun0 server push-route '172.16.42.0/24'

fix backported to crux

Can be set to finished on 1.3 Equuleus

https://vyos.readthedocs.io/en/latest/services/snmp.html#snmp-extensions

https://vyos.readthedocs.io/en/latest/services/snmp.html#snmp-extensions

You need to upload your script to /config/user-data, once done you can configure it via 'set service snmp script-extensions extension-name <extensionname> script <script_name>'

"cheat link here"
I tested and it works for me as expected. I also have a test record on the internal DNS server not in name space '.intern', so I checked everything not '.intern' goes to the DNS server 1.1.1.1. It seems the more specific wins.

Woah hang on.... we actually consulted the documentation on this?! That’s cheating

Is this what you expect?

strange, I just have to reboot again with same software version and now it looks good!!

I tested again with vyos-1.2.0-rolling+201907141109 but in recursor.conf the domain forwarding is missing (VyOS config is the same as in tests before):

The new implementation will behave as follows:

Fix is commited in current branch (rolling/Equuleus), it can be tested with the latest rolling build and task status updated.

Fixed by T1469 both in rolling and crux

I just tested with a split dns config (so I can exlude the internal DNS server has resolved the external domain name I used for the test). It works again!

Build complete

I supposed something like that :-) I will test and report

Please check wirh upcomming rolling release. There was a fix in T1469

in vyos-1.2.0-rolling+201907031336 now the dns forwarding domain entries are completely missing in recursor.conf:

in vyos-1.2.0-rolling+201906250337 dns forwarding domain doesn't work. Only the nameserver from 'name-server' are used.
In /etc/powerdns/recursor.conf it lokks like this now:

so I suppose something like: "set service snmp script1 [name path]" would do it?

For completeness, this was discussed in slack:

The garps should be send as they are being set per default to the values you have pasted from the documentation. Do you want to make that a config option to modify the defaults?

It will be good to have ability to configure followed GARP settings for individual VRRP groups or, at least for keepalived daemon overall, becouse in some situation switches can filter multiple ARP-packets, that is generated on transition.
In the process of migration to 1.2.1 we have discovered, that some GARP packets (we have 6 VRRP-groups on Interner interface) was filtered with ARP-spoofing filter by our ISP.
Problem was solved with VRRP-migration scripts, that execute some additional arping in ARP-Reply mode.

Please test with a rolling relase build date newer than 20120220 - Drivers have been replaced with the ones provided by Intel