https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162022-06-18T15:12:21ZpfSense bugtrackerpfSense - Bug #13282: Alias content is sometimes incomplete if the firewall cannot resolve an FQDN in the aliashttps://redmine.pfsense.org/issues/13282?journal_id=618392022-06-18T15:12:21ZSteve Wheeler
<ul><li><strong>Assignee</strong> set to <i>Reid Linnemann</i></li></ul> pfSense - Bug #13282: Alias content is sometimes incomplete if the firewall cannot resolve an FQDN in the aliashttps://redmine.pfsense.org/issues/13282?journal_id=620412022-06-30T17:04:18ZReid Linnemann
<ul></ul><p>There must be something else to this than just the unresolvable host, I've tried several times to replicate this and have been unsuccessful.</p>
<p>When you tested this, was there anything special about your resolver? Did you use dnsmasq or unbound, or were you configured to query name servers assigned manually or via DHCP?</p> pfSense - Bug #13282: Alias content is sometimes incomplete if the firewall cannot resolve an FQDN in the aliashttps://redmine.pfsense.org/issues/13282?journal_id=620602022-07-02T20:50:39ZKris Phillips
<ul></ul><p>Reid Linnemann wrote in <a href="#note-2">#note-2</a>:</p>
<blockquote>
<p>There must be something else to this than just the unresolvable host, I've tried several times to replicate this and have been unsuccessful.</p>
<p>When you tested this, was there anything special about your resolver? Did you use dnsmasq or unbound, or were you configured to query name servers assigned manually or via DHCP?</p>
</blockquote>
<p>Reid,</p>
<p>I was testing with unbound and DNS resolution was functional.</p>
<p>However, I just tried to recreate this on a fresh install of 22.05 RELEASE and I cannot. Last when I was testing this I was on RC4 or 5 and could reproduce it regularly. Not sure what changed or if there was some other circumstance to this that I'm no longer hitting (maybe a package or another remnant of my testing). Where there any changes between the RC and release to the functions here or PHP?</p> pfSense - Bug #13282: Alias content is sometimes incomplete if the firewall cannot resolve an FQDN in the aliashttps://redmine.pfsense.org/issues/13282?journal_id=621742022-07-12T17:26:47ZReid Linnemann
<ul></ul><p>No, none that I am aware of. I know that filterdns has been untouched for a few months now. I'll look for changes elsewhere that could be related.</p> pfSense - Bug #13282: Alias content is sometimes incomplete if the firewall cannot resolve an FQDN in the aliashttps://redmine.pfsense.org/issues/13282?journal_id=621752022-07-12T17:55:14ZChris Linstruth
<ul></ul><p>This has been squirreley for a long time and has been very difficult to reliably duplicate but it is very real. <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Alias content is sometimes incomplete when an alias contains both FQDN and IP address entries (Resolved)" href="https://redmine.pfsense.org/issues/9296">#9296</a> as stated earlier.</p> pfSense - Bug #13282: Alias content is sometimes incomplete if the firewall cannot resolve an FQDN in the aliashttps://redmine.pfsense.org/issues/13282?journal_id=621762022-07-12T17:57:41ZReid Linnemann
<ul></ul><p>I trust that it is definitely real and not a false or misinterpreted report. There's a reason for it and with enough tenacity I'll find it.</p> pfSense - Bug #13282: Alias content is sometimes incomplete if the firewall cannot resolve an FQDN in the aliashttps://redmine.pfsense.org/issues/13282?journal_id=630602022-10-04T12:41:32ZReid Linnemann
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Target version</strong> set to <i>23.01</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>I'm pretty sure the invalid FQDN is a red herring, I found a lot of thread synchronization issues with filterdns that should be resolved as of <a class="external" href="https://github.com/pfsense/FreeBSD-ports/commit/eebf583cb47ad8255f3890b66349f8eb7d66bc95">https://github.com/pfsense/FreeBSD-ports/commit/eebf583cb47ad8255f3890b66349f8eb7d66bc95</a></p> pfSense - Bug #13282: Alias content is sometimes incomplete if the firewall cannot resolve an FQDN in the aliashttps://redmine.pfsense.org/issues/13282?journal_id=642922022-12-07T11:54:18ZJim Pingle
<ul><li><strong>Project</strong> changed from <i>pfSense Plus</i> to <i>pfSense</i></li><li><strong>Subject</strong> changed from <i>FQDN Aliases Break if an Invalid Domain is Present in the Chain</i> to <i>Alias content is sometimes incomplete if the firewall cannot resolve an FQDN in the alias</i></li><li><strong>Category</strong> changed from <i>Aliases / Tables</i> to <i>Aliases / Tables</i></li><li><strong>Target version</strong> changed from <i>23.01</i> to <i>2.7.0</i></li><li><strong>Affected Plus Version</strong> deleted (<del><i>22.05</i></del>)</li><li><strong>Plus Target Version</strong> set to <i>23.01</i></li></ul><p>Updating subject for release notes.</p> pfSense - Bug #13282: Alias content is sometimes incomplete if the firewall cannot resolve an FQDN in the aliashttps://redmine.pfsense.org/issues/13282?journal_id=648582022-12-23T08:53:46ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Hard to reproduce this but at least as stated it appears to be OK. I tried a few variations and every time the table contained the expected data. Can always reopen/revisit if need be, though there is more significant filterdns work coming in the next release that will likely render this moot either way.</p>