https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162017-10-29T12:49:43ZpfSense bugtrackerpfSense - Bug #8001: Invalid FQDN in alias causes alias table to fail *silently*https://redmine.pfsense.org/issues/8001?journal_id=347972017-10-29T12:49:43ZLuiz Souzaluiz@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Luiz Souza</i></li></ul> pfSense - Bug #8001: Invalid FQDN in alias causes alias table to fail *silently*https://redmine.pfsense.org/issues/8001?journal_id=348052017-10-30T11:26:03ZStuart Wyattstuart@wyatt.pops.net
<ul></ul><p>More specifically, in this case, the FDQN timed out (DNS didn't respond).</p> pfSense - Bug #8001: Invalid FQDN in alias causes alias table to fail *silently*https://redmine.pfsense.org/issues/8001?journal_id=351632017-11-16T12:51:37ZJim Pingle
<ul><li><strong>Target version</strong> changed from <i>2.4.2</i> to <i>2.4.3</i></li></ul> pfSense - Bug #8001: Invalid FQDN in alias causes alias table to fail *silently*https://redmine.pfsense.org/issues/8001?journal_id=357082018-02-01T12:31:34ZAnonymous
<ul><li><strong>Target version</strong> changed from <i>2.4.3</i> to <i>2.4.4</i></li></ul> pfSense - Bug #8001: Invalid FQDN in alias causes alias table to fail *silently*https://redmine.pfsense.org/issues/8001?journal_id=376842018-08-14T13:53:19ZAnonymous
<ul><li><strong>Target version</strong> changed from <i>2.4.4</i> to <i>48</i></li></ul> pfSense - Bug #8001: Invalid FQDN in alias causes alias table to fail *silently*https://redmine.pfsense.org/issues/8001?journal_id=382722018-09-06T15:00:52Z→ luckman212luke.hamburg@gmail.com
<ul></ul><p>possibly related bug: <a class="external" href="https://redmine.pfsense.org/issues/8758">https://redmine.pfsense.org/issues/8758</a></p> pfSense - Bug #8001: Invalid FQDN in alias causes alias table to fail *silently*https://redmine.pfsense.org/issues/8001?journal_id=391962018-11-09T07:28:31ZLuiz Souzaluiz@netgate.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Should be fixed by the new filterdns (see <a class="issue tracker-1 status-5 priority-5 priority-high4 closed" title="Bug: filterdns stops working on a regular basis. (Closed)" href="https://redmine.pfsense.org/issues/8758">#8758</a> too).</p>
<p>If you have issues, please let us know.</p> pfSense - Bug #8001: Invalid FQDN in alias causes alias table to fail *silently*https://redmine.pfsense.org/issues/8001?journal_id=391972018-11-09T07:57:26ZRenato Botelhorenato@netgate.com
<ul><li><strong>Target version</strong> changed from <i>48</i> to <i>2.4.4-p1</i></li></ul> pfSense - Bug #8001: Invalid FQDN in alias causes alias table to fail *silently*https://redmine.pfsense.org/issues/8001?journal_id=393002018-11-18T19:27:45ZChris Linstruth
<ul></ul><p>Created host alias with these FQDNs</p>
<p><a class="external" href="http://www.pfsense-bug-8001.com">www.pfsense-bug-8001.com</a><br /><a class="external" href="http://www.google.com">www.google.com</a><br /><a class="external" href="http://www.yahoo.com">www.yahoo.com</a><br /><a class="external" href="http://www.netgate.com">www.netgate.com</a><br /><a class="external" href="http://www.pfsense.org">www.pfsense.org</a></p>
<p>pfsense-bug-8001.com was forwarded to an unresponsive address.</p>
<p>Alias populated with the rest of the names' corresponding A and AAAA records.</p>
<p>Looks OK to me.</p> pfSense - Bug #8001: Invalid FQDN in alias causes alias table to fail *silently*https://redmine.pfsense.org/issues/8001?journal_id=393052018-11-19T05:37:52ZLuiz Souzaluiz@netgate.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>Thanks!</p> pfSense - Bug #8001: Invalid FQDN in alias causes alias table to fail *silently*https://redmine.pfsense.org/issues/8001?journal_id=393072018-11-19T10:59:21ZStuart Wyattstuart@wyatt.pops.net
<ul></ul><p>Verified that the bad FQDN doesn't fail the tables any longer.</p>
<p>There's still no error. There should at least be a warning to help the user find the mistake.</p>