Project

General

Profile

Actions

Bug #14734

open

Alias FQDN resolving issue results in incomplete tables

Added by Robert Gijsen 8 months ago. Updated 8 months ago.

Status:
New
Priority:
High
Assignee:
-
Category:
Aliases / Tables
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.0
Affected Architecture:
amd64

Description

In CE 2.7.0, there are still issues when FQDN are used in aliasses. Vonsider an alias with 3 entries, 2 static IP's and one FQDN, pointing to one of those IP's as well. When the FQDN changes to the other IP, the IP it had initially is gone from the table.

Steps to reproduce:

Create an alias
  • add 1.1.1.1
  • add 8.8.8.8
  • add a (public) dns entry you created, pointing to 1.1.1.1, ie pfsensetest.domain.com
  • monitor the table-entry for the alias, all will be ok
  • now change the DNS entry for pfsensetest.domain.com from 1.1.1.1 to 8.8.8.8 and wait for it to be replicated and pfSense to pick it up
  • in my setups, 1.1.1.1 got deleted from the table. So while 8.8.8.8 is in there 'twice' now, and 1.1.1.1 only once statically, it's not there anymore
  • killing filterdns and reloading filters repopulates the tables correctly it seems.

It looks like when the FQDN is resolved, it overrules the static entry if one with the same value exists, and when the FQDN changes, the static entry is not put back in to the table. I tailed resolver.log while reproducing the issue, but it made no notion at all of resolving the FQDN to another IP. So I don't know what log to add, or which log to enable verbose logging for.

I consider this high priority, as it has high potential of actually functionally breaking an environment.

Actions #1

Updated by Robert Gijsen 8 months ago

Actions

Also available in: Atom PDF