Show Posts
1
15.7 Legacy Series / [SOLVED] Sync of /etc/hosts in HA Configuration failure
« on: August 27, 2015, 01:29:12 pm »
Hi,
I have two opnsense instances running in a HA config with xmlrpc sync activated. The config is synced fine but it doesn't seem to be activated on the second system. For example dnsmasq and the entries inside /etc/hosts
When I add a new host in the dns forwarder (for example host01 with the ip 192.168.1.1) then it gets activated on the first gateway and the dns resolutions works fine.
gateway01, $ cat /etc/hosts:
...
192.168.1.1 host01.foo.dom host01
...
on the second gateway(02) in the web gui the host is shown but in the /etc/hosts its missing, resulting in a dns failure.
The workaround is to restart the gateway02 (the whole system, not only the service), then the entries are synced.
In addition, on the second opnsense the /etc/hosts contains duplicate entries from dhcp (pool) leases.
This doesn't look like production ready.
Any hints how to solve it?
Best regards!
I have two opnsense instances running in a HA config with xmlrpc sync activated. The config is synced fine but it doesn't seem to be activated on the second system. For example dnsmasq and the entries inside /etc/hosts
When I add a new host in the dns forwarder (for example host01 with the ip 192.168.1.1) then it gets activated on the first gateway and the dns resolutions works fine.
gateway01, $ cat /etc/hosts:
...
192.168.1.1 host01.foo.dom host01
...
on the second gateway(02) in the web gui the host is shown but in the /etc/hosts its missing, resulting in a dns failure.
The workaround is to restart the gateway02 (the whole system, not only the service), then the entries are synced.
In addition, on the second opnsense the /etc/hosts contains duplicate entries from dhcp (pool) leases.
This doesn't look like production ready.
Any hints how to solve it?
Best regards!