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 firewallI use DNS Forwarder.After changing the alias to IP it's working but not preferred.

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?

Logged

- An intelligent man is sometimes forced to be drunk to spend time with his fools.- Please don't PM me for personal help- if you want to say thanks applaud or https://www.freebsdfoundation.org/donate/1x SG-2440 2.4.2-RELEASE-p1 (work)1x SG-4860 2.4.2-RELEASE-p1 (home)

Alias:IP_Syncthing_Clients - Type: Hosts - Entries: (contains many local computer names all registered in DNS by pfSense DHCP Server) my-desktopIP_NAS - Type: Hosts - Entries: nas.fqdn.privatePort_Syncthing_Server_TCP- Type: Ports - Entries: 22000Looking at the table alias for IP_Syncthing_Clients confirms that the IP address for my-desktop is in there.The table alias for IP_NAS says there are no entries in the table. I have tried amending both the description and added a new host name to prompt it to refresh it but still it reports there are no entries in the table.Port_Syncthing_Server_TCP doesn't appear in the tables list (I'm assuming only IP ones will?)

Packets destined to port 22000 on nas.fqdn.local from my-desktop are blocked. If I change the rule and replace IP_NAS with the IP address of NAS it works fine.

So it looks like if the table entries are missing it won't resolve. So it looks like the upgrade is hosing some of the Alias tables (as there are a lot of empty ones). Which begs the question how to recreate the alias tables without starting from scratch.

These rules have been in place since 19/2/16 without issue. There are also other rules I have with the same problems. This is just one.

Dude post up screenshots of your alias and your diagnostic table... How and the hell is pfsense going to resolve smtp.domain.local since that is not a public..

So your saying that is a reservation in your dhcp that your register in your forwarder? Or your just registering dhcp clients? If your not doing an override

If your saying pfsense can resolve it, then it would be in the TABLE.. If its not in the table then no your alias would not work.

Can not duplicate this.. Plain and simple.. If pfsense can resolve a fqdn, then it shows up in the table.. Be it a local entry or a public entry..

Logged

- An intelligent man is sometimes forced to be drunk to spend time with his fools.- Please don't PM me for personal help- if you want to say thanks applaud or https://www.freebsdfoundation.org/donate/1x SG-2440 2.4.2-RELEASE-p1 (work)1x SG-4860 2.4.2-RELEASE-p1 (home)

Strange:Since update on Friday until yesterday the firewall was blocking the smtp port.Yesterday I saved this table entry again in the hope it would work, but it always blocked this port.Only changing to IP resolved this problem.Today after trying multiple entries with google it's working again.Now I have a FQDN entry and the firewall is open again. WTF?

Strange:Since update on Friday until yesterday the firewall was blocking the smtp port.Yesterday I saved this table entry again in the hope it would work, but it always blocked this port.Only changing to IP resolved this problem.Today after trying multiple entries with google it's working again.Now I have a FQDN entry and the firewall is open again. WTF?

Glad you got yours sorted. I only upgraded yesterday so hopefully I don't need to wait 4 days before it starts working again!

I have a mixture of internal and external addresses that are in the aliases. All resolve through Diagnostics -> Ping so pfSense knows how to resolve them. But their tables are empty.

This is a outside located perimeter firewall and is connected with the core network over openvpn.In the core network are the smtp and the dns servers. The domain.local TLD is forwarded with Domain Override.This solution (openvpn, dns forward, fqdn alias) is working since years.

I don't know what happened after update that this solution was so much disturbed.Normally the tables should be reloaded with interface changes and everything should be alright.

1. guess: It didn't refresh the alias table even on saving old entries2. guess: It look like there was a negative DNS cache entry for the alias tables which didn't expire if it's always used. While booting the FQDN couldn't be resolved.

I just tried to Diagnostics -> Ping 'hello.fqdn.private' and just 'hello' and both failed as you'd expect.

UPDATED: Also tried this from the console itself with the same error (again as you'd expect). I rebooted pfSense earlier today and also about 15 minutes ago (in case the aliases 'spring' to life after a reboot - I can but hope).