In T1416#40429, @zsdc wrote:@thinkl33t, recommended way is using dynamic-dns-update, all other ways are not recommended to use at this moment.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Feb 26 2024
Feb 26 2024
Sep 19 2019
Sep 19 2019
thinkl33t added a comment to T1416: 2 dhcp server run in failover mode can't sync hostname with each other.
Jul 26 2019
Jul 26 2019
thinkl33t added a comment to T1416: 2 dhcp server run in failover mode can't sync hostname with each other.
Yeah, I'd mark this not-a-bug. Update the documentation to mention hosts file update with failover doesn't maintain consistent state between failover servers.
Jun 13 2019
Jun 13 2019
thinkl33t added a comment to T1076: SSH: make configuration (sshd_config) volatile and store it to /run.
Could we work around this by implementing an overlay for every commit, with the entire stack of overlays being combined with the root overlay when a save is issued?
Mar 12 2019
Mar 12 2019
I've finally managed to test this (apologies, we've had a super busy couple of months) and don't appear to be able to connect to the VPN anymore :(
Mar 11 2019
Mar 11 2019
thinkl33t added a comment to T1285: Kernel issues with 1.2.0 & 1.2.0-rolling+201903060337 causing lockup.
I've put in the suggested kernel parameters for my install to disable the broken functionality. Hopefully this will keep it stable until a version with an upgraded kernel is available :)
thinkl33t added a comment to T1285: Kernel issues with 1.2.0 & 1.2.0-rolling+201903060337 causing lockup.
This debian bug shows the same issue:
thinkl33t added a comment to T1285: Kernel issues with 1.2.0 & 1.2.0-rolling+201903060337 causing lockup.
Full lspci -vv
thinkl33t added a comment to T1285: Kernel issues with 1.2.0 & 1.2.0-rolling+201903060337 causing lockup.
Its the intel broadwell one:
Mar 7 2019
Mar 7 2019
thinkl33t added a comment to T1285: Kernel issues with 1.2.0 & 1.2.0-rolling+201903060337 causing lockup.
Its a pair of supermicro servers, each containing:
Mar 6 2019
Mar 6 2019
Feb 25 2019
Feb 25 2019
We've not had this issue since i applied the patch.
Feb 18 2019
Feb 18 2019
Brill, i've applied that patch and will keep an eye on it for a few days to see what happens.
The line giving the error is:
Feb 12 2019
Feb 12 2019
> show service dhcp-server hostfile-update shared-network-name VLAN101 subnet 172.16.101.0/24 { default-router 172.16.101.254 dns-server 172.16.101.254 domain-name guest.example.org lease 3600 range 0 { start 172.16.101.1 stop 172.16.101.250 } } }
Jan 28 2019
Jan 28 2019
Note that this has taken down DNS on our firewall (and hence our network) a couple of times now, both annoyingly early in the morning when nobody was in to fix it.
thinkl33t updated the task description for T1211: Blank hostnames from dhcpd are able to bring down DNS.
thinkl33t created T1211: Blank hostnames from dhcpd are able to bring down DNS in the S1 VyOS Public space.
Jan 15 2019
Jan 15 2019
I've implemented this in our ansible-derived vyos configuration by allowing the static addresses to be generated with the VLAN prepended and adding a system static-host-mapping for the fqdn to ip.
Nov 27 2018
Nov 27 2018
Actually, I managed to get this working by passing the following:
Nov 8 2018
Nov 8 2018
thinkl33t added a comment to T976: /etc/hosts is not updated when using hostfile-update on dhcp server in rc5.
I've done a bit of fiddling with this today on a test VyOS 1.2.0-rc6, Attempting to set a custom option and pass it through to the leases file. Unfortunately I wasn't successful.
Nov 7 2018
Nov 7 2018
thinkl33t added a comment to T976: /etc/hosts is not updated when using hostfile-update on dhcp server in rc5.
It looks like this change was made in https://phabricator.vyos.net/T726 before the python rewrite.
Aug 2 2018
Aug 2 2018
May 25 2018
May 25 2018
May 23 2018
May 23 2018
pdns doesn't have a built-in reload (at least not available through systemd), but i've just tested and the following works: