I've setup a list of aliases on my 2.0.2 embedded box, which are DNS names.
This alias is then used for a floating rule which then matches traffic for
my Traffic Shaping rules.
However, the data does not go into the correct stream - it seems to be
matching to my HTTP traffic queue, which has too low priority.

The rule for this connection is higher than the HTTP traffic rule.

Specifically, 'prem2.di.fm' resolves to '79.141.174.3' when using a lookup
tool (Windows7 'nslookup' in this case). My Traffic Queues sugest that when
using the DNS name, it does not go into the correct queue. I have manually
added the IP to the alias entry (so i now have 'prem2.di.fm' and
'79.141.174.3' in the same alias entry) and this now works correctly -
obviously the addition of the IP address has made this work as expected.

have I misunderstood the limitations of aliases/another part of pfsense,
should DNS resolution in Alias lists work as I expect it to?

thanks for any info!
Tim
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to