fix backported to crux

I wonder if the bgp daemon is being started before the hostname is changed by the config script. Seems possible since we added a lock so it executes later.

@zsdc Hostname is still showing as 'debian' in 1.2.0-rolling+201907191807

https://github.com/vyos/vyos-netplug/commit/81fd74bfbfa6daed506693ecc20deff09042bc71 broke it, I have to find out why he commited it.

I'll set up monitoring, sure.

I have ran VyOS 1.2.1 and now 1.2.2 for quiet some time and can no longer see this issue. 1.2.1 and 1.2.2 are both based on PowerDNS recursor 4.1 series.

Can be set to finished on 1.3 Equuleus

That's unfortunate. I've had to restart dns every few days at some clients due to an outage because of this bug. It would be not nice if it were to regress. Is there a way to build on buster with newer packages?

Unfortunately PowerDNS no longer supports the 4.2 series on Debian oldoldstable (Jessie) - reverting this on current to fix the build.

fixed via https://phabricator.vyos.net/T1065

https://github.com/vyos/vyatta-ipv6-rtradv/commit/2c543f7f369f9429e7dad89bb7bb9f9dec823856

This also affect manually built iso's that also fails because of pdns-recursor

Hi! The rolling release is broken because pdns-recursor has stopped to provide packages for jessie and the current index points to a file that is currently not available. We are working on fixing this and it migth be that we need to start building it ourself instead.

The problem, which leads to the malformed hostname in Hostname Capability was fixed in T1531. I am marking this as "Resolved", because the problem with DNS servers was resolved also, according to feedback.

Please backport to Crux.

closed as requested since there is no need for a new implementation.

Update:
I did tested several server-related option combinations, such as "--ping-restart 0", "--reneg-sec 0", "--reneg-sec 36000"(10h).
Then I realized that I might interpreted --reneg-sec option incorrectly. As stated in(read text in bold) https://openvpn.net/community-resources/reference-manual-for-openvpn-2-3/ :

This is really a broken abstraction. There is no separate namespaces for IPv4 and IPv6 groups in IPset.
We'll have to autoprefix the groups or similar, if we want it to work that way.

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

@dienac Any results to share?

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>'

Noticed this today. Possibly another related bug, seems to have appeared the same time the previous ones were fixed. Hostname in bgp is showing up as 'debian', the hostname command, /etc/hostname, /etc/resolv.conf show the correct hostname.

"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.

It will be definately a Kernel issue. I will close this now as it seems to be resolved. Please re-open when the issue re-appears on a new update of the kernel.

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:

After reading the PowerDNS docs this should be correct: forward-zones-recurse=.=1.1.1.1,intern=172.16.10.1 I will take a look.

Same issue present in 1.3

test config looks like this:

From the slack discussion, we found there should be a single forward-zones-recurse line as the last one takes precedence

Can you share your configuration and the actual /etc/powerdns/recursor.conf file? And an expected /etc/powerdns/recursor.conf?

It worked as it looked like this:

How should the config look like?

recursor.conf looks like this:

The problem is back in 1.2.0-rolling+201907110337 :-(
The line with the forwarders in recursor.conf is missing again.
@c-po
How can I reopen this task here?