Table entries added by filterdns can clobber overlapping hardcoded entries during DNS changes
|Affected version:||Affected Architecture:|
If filterdns resolves a record to an IP that exists in a table, and then later switches away, the hardcoded IP will be lost.
A practical example, have an alias with this:
Initially, myhost.dyndns.org would resolve to something else, say 126.96.36.199. The table now contains:
Then the myhost.dyndns.org user visits the site with 188.8.131.52, which filterdns picks up. The table now contains:
The myhost.dyndns.org user leaves again, and myhost.dyndns.org resolves to 184.108.40.206. The table now contains:
The original hardcoded 220.127.116.11 is lost because filterdns removed it during the last switch.
#2 Updated by Ermal Luçi 4 months ago
- % Done changed from 0 to 100
Applied in changeset pfsense-tools:6f436e9ddf46e64e9b6d87d587a63242b4063d0d.