2.0.x firewall – Do rules support reverse hostname lookups?



  • I remember reading in the past that in 2.0.x there would be support for reverse hostname lookups that could be used in firewall rules.

    An example of its use could be something like…

    Using Dyndns on clientA to access remotely firewallA where firewallA only accepts access on port 22 / 443 for the statically set hostname in the rules which clientA uses.

    Just curious, didn't see it in the changelog.  Thanks.


  • Rebel Alliance Developer Netgate

    It isn't "reverse" lookups in that way. You can add hostnames to an alias. Periodically, these are resolved again to ensure the IPs are up to date. They are used like any other IP-based alias entry.



  • Thx Jimp.

    http://forum.pfsense.org/index.php/topic,39627.0.html  (same topic discussed here also, Jimp response more thorough)

    @jimp:

    It isn't "reverse" lookups in that way. You can add hostnames to an alias. Periodically, these are resolved again to ensure the IPs are up to date. They are used like any other IP-based alias entry.


Locked