2.7.0 - Alias FQDN bug still present
-
Hi,
unfortunately I found that bug #9296 is still present. I've updated the bugreport, but not sure if anyone reads closed tickets. Basically alias entries still get removed on certain instances, and one way to reproduce is the following:- Create an alias
- add 1.1.1.1
- add 8.8.8.8
- add a 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 from 1.1.1.1 to 8.8.8.8 and wait for it to be replicated ans pfSense to pick it up
- in my setup, 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, it's not there anymore
- killing filterdns and reloading filters repopulates the tables correctly it seems.
Tried 3 times, all with the same results.
Hope this can get fixed (again?).
-
So this only happens when you update a locally defined DNS host override? And the old entry is removed entirely even though it's defined twice?
That seems different to the original definition of that bug. It should probably be a new bug if one doesn't already exist that covers that.
-
@stephenw10 I create a public DNS record 8.8.8.8, and have an alias with that record in, as well as 1.1.1.1 and 8.8.8.8 'manually'. So three entries in that alias. Then I change the public DNS entry to 1.1.1.1. Then, 8.8.8.8 gets removed from the table.
It looks as if the FQDN, which was 8.8.8.8 before, overrules the manually configured 8.8.8.8 entry, but then when that FQDN changes, the manually configured value it had before, isn't repopulated to the table. I think in 2.6 (and before) at least one of the ways to reproduce the issue in https://redmine.pfsense.org/issues/9296 was exactly that.
Btw I will try to reproduce this on 23.05.1 as well, will post here with the results. Might be able to do that tonight.
-
@rgijsen said in 2.7.0 - Alias FQDN bug still present:
killing filterdns and reloading filters repopulates the tables correctly it seems.
The original bug though did not do that^. That part is fixed which is why I suggested a new bug (or if there is another open one).
It appears the code removes the old entry from the table but over matches and also removes the static entry. -
@stephenw10 Well, in 2.6 and before, since hitting that nasty FQDN bug, restarting filterdns and reloading filters DID work for us. Temporary of course, but it did work. I think multiple people (myself included) reported that in https://redmine.pfsense.org/issues/9296.
For what it's worth, I tested this same alias on 23.05.1 on a 1100 and 2100 and it seems they do not suffer this issue.
-
Hmm, that's curious. I wonder if it could be a timing issue...
