Hmm, I have 7.1-dev-1~debian8+1 on a rolling and 3 blackhole routes and no issues at all.

Con you provide a configuration to reproduce the issue?

server OK but now we get ERROR:
Feb 2 16:51:21 VyosCP ddclient[5968]: FAILED: updating is: notfqdn: A Fully-Qualified Domain Name was not provided
Feb 2 16:56:21 VyosCP ddclient[5968]: WARNING: file /var/cache/ddclient/ddclient.cache, line 5: Invalid Value for keyword 'ip' = ''
Feb 2 16:56:22 VyosCP ddclient[5968]: FAILED: updating is: notfqdn: A Fully-Qualified Domain Name was not provided
Feb 2 17:05:28 VyosCP ddclient[4710]: WARNING: file /var/cache/ddclient/ddclient.cache, line 5: Invalid Value for keyword 'ip' = ''
Feb 2 17:05:36 VyosCP ddclient[4710]: FAILED: updating is: notfqdn: A Fully-Qualified Domain Name was not provided

After some more playing with it ... it solves the problem reproducibly to have staticd=yes included and NOT have the null route anywhere.

It solved it for me yesterday. After some more playing today this now seems to be a frr bug.

@primoz Adding staticd to the daemons config fixes the issue reproducibly on affected systems, even after reboot?

I can confirm this. 1.2.0-EPA3 does not have thisbissue but 1.2.0 has it.

There might actually be a bit of a deeper problem here, somewhat conditional on some static interface routing. On an broken system, it does say something about staticd starting

Wierd, i cannot reproduce this on LTS 1.2.0 on both baremetal and virtual instances.

to /etc/frr/daemons (+ restarting frr) seems to fix this.

And more info:

I tracked down what is causing this.

http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyos-1x/vyos-1x_1.2.0-11_all.deb or next rolling release will have the fix.