pfSense English Support > Installation and Upgrades

Upgrade 2.4.0: firewall rule with alias and FQDN not working anymore

(1/8) > >>

After upgrade the ports are closed.

Diagnostic->Ping is working.
I saved the alias again to force dns lookup.
still unchecked (never enabled before): Do not use the DNS Forwarder/DNS Resolver as a DNS server for the firewall
I use DNS Forwarder.
After changing the alias to IP it's working but not preferred.

--- Code: --- <alias>
<descr><![CDATA[SMTP Server]]></descr>
<detail><![CDATA[Entry added Fri, 14 Sep 2012 13:58:06 +0000]]></detail>
--- End code ---

--- Code: --- <rule>
<statetype><![CDATA[keep state]]></statetype>
<descr><![CDATA[SMTP Server]]></descr>
--- End code ---

I have EXACTLY the same issue although I'm using DNS Resolver and not DNS Forwarder. As many many of my rules rely on aliases (and names) it's broken the best part of my network.

I opened a bug for this:

You opened a bug report with ZERO info to suggest it is..

So you have an alias for smtp.domain.local as a fqdn in it..

Does this resolve?  Simple query to pfsense for that fqdn should show you if pfsense can resolve it.  Or simple dns lookup under diag.

What does the table for your alias show also under diag..  As the comment in the bug you created states.. They can not duplicate your problem, nor can I..

Where should smtp.domain.local resolve?  Is this a host override on pfsense?  reservation in dhcp that you have register in forwarder/resolver?  Is it some downstream dns that should resolve that?  If so do you have a domain override in place so pfsense knows where to go ask for smtp.domain.local?

Can you read?

> Diagnostic->Ping is working.

And it worked before update!


[0] Message Index

[#] Next page

Go to full version