Project

General

Profile

Actions

Bug #13184

closed

pfSense 2.6.0 CE alias table not populated if entries contain at lease one FQDN

Added by Tom Huerlimann over 2 years ago. Updated over 2 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Aliases / Tables
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.6.0
Affected Architecture:
amd64

Description

Steps to reproduce

1. Login to pfsense WebGUI

2. Firewall > Aliases

3. Name = Test

4. Type = Host(s)

5. FQDN = any (example update.microsoft.com)

6. Click "Save"

7. Login to pfsense SSH console

8. # cat /var/log/resolver.log | grep -i update.microsoft.com
May 19 17:59:54 gw-wan-001 filterdns14762: Adding Action: pf table: Test host: update.microsoft.com
May 19 17:59:54 gw-wan-001 filterdns14762: Adding host update.microsoft.com

9. # pfctl -T show -t Test

-> Empty

10. # nslookup update.microsoft.com
Server: 62.2.17.61
Address: 62.2.17.61#53

Non-authoritative answer:
update.microsoft.com canonical name = update.microsoft.com.nsatc.net.
update.microsoft.com.nsatc.net canonical name = www.update.microsoft.com.nsatc.net.
www.update.microsoft.com.nsatc.net canonical name = redir.update.microsoft.com.nsatc.net.
redir.update.microsoft.com.nsatc.net canonical name = redir.update.msft.com.trafficmanager.net.
Name: redir.update.msft.com.trafficmanager.net
Address: 20.109.209.108

-> Nslookup working.

Any idea why this is happening?

Best regards
Tom

Actions #1

Updated by Jim Pingle over 2 years ago

  • Status changed from New to Not a Bug
  • Priority changed from Very High to Normal

This site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .

See Reporting Issues with pfSense Software for more information.

Actions #2

Updated by Tom Huerlimann over 2 years ago

It‘s not a request for support, it‘s a request to fix a bug. Can you please mark it as a bug and increase priority as a core functionality is affected?

Please see:
https://redmine.pfsense.org/issues/9296

Thank you

Actions #3

Updated by Jim Pingle over 2 years ago

It was worded as a support question, not a bug report.

The issue you linked is still open, therefore this is redundant as a bug report as well.

Either way it's invalid and doesn't belong here.

Actions #4

Updated by Tom Huerlimann over 2 years ago

I'm sorry for the wrong wording and please excuse that i did not see that the other one is still confirmed.

I saw the other case is marked as 100 % done - it made me feel that the other cases is out of focus.

Can we bring this into focus? I see the other case is also with priority 'low', unacceptable from my point of view.

Thank you

Actions #5

Updated by Tom Huerlimann over 2 years ago

My issue has been solved: https://docs.netgate.com/pfsense/en/latest/troubleshooting/filterdns-thread-errors.html

Sorry for not checking this first. Thank you.

best regards
Tom

Actions

Also available in: Atom PDF