Invalid FQDN in alias causes alias table to fail *silently*
When you have a FQDN in an alias ans the FQDN does not resolve, the alias table creation will not happen and any other aliases that use the alias will be truncated or fail.
The root cause can be user error, but there's nothing in the system log or the firewall rebuild monitoring that indicates the failure.
This can cause a unexpected hole in the firewall, even though everything looks like it worked in the GUI.
- Assignee set to Luiz Souza
More specifically, in this case, the FDQN timed out (DNS didn't respond).
- Target version changed from 2.4.2 to 2.4.3
- Target version changed from 2.4.3 to 2.4.4
- Target version changed from 2.4.4 to 48
- Status changed from New to Feedback
- % Done changed from 0 to 100
Should be fixed by the new filterdns (see #8758 too).
If you have issues, please let us know.
- Target version changed from 48 to 2.4.4-p1
- Status changed from Feedback to Closed
Verified that the bad FQDN doesn't fail the tables any longer.
There's still no error. There should at least be a warning to help the user find the mistake.
Also available in: Atom