Bug #117: dns forewarder + carp not working properly - pfSense - pfSense bugtracker

Actions

Copy link

Bug #117

closed

dns forewarder + carp not working properly

Added by Nico de Haer about 15 years ago. Updated over 14 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Unknown

Target version:

2.0

Start date:

10/21/2009

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

Affected Architecture:

Description

I have two pfsense boxes: core-01a and core-01b. The two boxes have a working carp setup on the LAN side. IP's are:
172.20.0.1 for carp
172.20.0.2 for core-01a
172.20.0.3 for core-01b

tickbox is ticked for 'Synchronize DNS Forwarder'

When I add a new host to the list under 'Services: DNS forwarder' it does not get synced to the backup pfsense. If I then click on the 'save' button in 'Services: CARP Settings: Edit' to force a configuration sync it does show up on the backup pfsense.

I can reproduce this on both v 1.2.2 and 1.2.3rc3

Actions

Copy link

Updated by Scott Ullrich about 15 years ago

Status changed from New to Resolved

sullrich pushed 020d757a to pfsense/mainline on branch master
Reload filter in case we need to sync CARP data
sullrich pushed ced6d6df to pfsense/mainline on branch RELENG_1_2
Reload filter in case we need to sync CARP data

This should be resolved now. Thank you for the report.

Actions

Copy link

Updated by Olivier Le Cam over 14 years ago

Scott Ullrich wrote:

This should be resolved now. Thank you for the report.

It seems that it is not 100% resolved. Although the backup pfSense has its DNS Forwarders synced in the web interface, the /var/etc/hosts file is not updated.

This apply here to 1.2.3-RELEASE (built on Sun Dec 6 23:21:36 EST 2009).

--
Olivier

Actions

Copy link

Updated by Chris Buechler over 14 years ago

Status changed from Resolved to Feedback
Priority changed from High to Normal
Target version changed from 1.2.3 to 2.0
Affected Version deleted (~~1.2.2~~)

Moving to feedback to verify this functionality on 2.0.

Actions

Copy link

Updated by Jim Pingle over 14 years ago

Status changed from Feedback to New

The settings sync to the slave but the service isn't restarted, so any change in hostnames or even the register DHCP hostname settings will not activate on the backup after sync.

As with some other components, there may need to be a hook or extra code in the sync to give this a kick post-sync. (Like we do for OpenVPN)

Actions

Copy link