On 2012-03-14 16:27, Jim Pingle wrote:
On 3/14/2012 4:10 PM, Ugo Bellavance wrote:
I know it is less secure and creates load on the firewall and DNS
servers, but is it possible to create an alias to create rules, that
would allow one to deny traffic for hosts that has a PTR that contains a
string?

DNS resolution in the ruleset is done (per my last e-mail) independently
of the actual incoming packets. Even in pf if you use a hostname in a
rule it's resolved at filter load. There isn't a way for it to check the
ptr of an IP in that way. It would always be a forward DNS lookup.

Not sure what problem you're looking to solve there, if you're looking
to block something, PTRs would be pretty unreliable since they rarely
(except for mail servers) reverse resolve to the same IP as the forward
name for many public-facing servers.

My current CheckPoint does it, but it clearly states that the rules using this kind of criteria should be put at the end to limit the number of DNS requests that are necessary.

We are using it for a few rules, where we couldn't find the IP ranges for a bunch of web servers, but they do have something in common in their PTR record.

I can live without that.

Thanks,

Ugo


_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to