topic Re: Feature Request - DNS name as source/destination in General Topics

Feature Request - DNS name as source/destination

nrouten — Wed, 26 May 2010 15:00:01 GMT

It would be very useful to use a public DNS name as a source address or destination address directly in Security Rules. Currently, a domain/category etc.. can be blocked or allowed through the URL filter as a destination. However this can make the single outbound rule function as an end allow and end deny. This is a challenge if you need additional outbound policies to be evaluated for match further down in order or if there are rules setup as an IDS/IPS.Does that make sense? Maybe I'm not aware of a way to already do this.

Re: Feature Request - DNS name as source/destination

swhyte — Wed, 26 May 2010 21:35:56 GMT

Hello Nrouten,

this is a popular request that should be considered on our road map. Please submit a feature/enhancement request through your sales contact in order this can be pushed.

thanks,

Stephen

Re: Feature Request - DNS name as source/destination

nrouten — Thu, 27 May 2010 20:52:19 GMT

Great, thank you. We submitted the request awhile back.

Re: Feature Request - DNS name as source/destination

ksalustro — Wed, 17 Nov 2010 18:22:52 GMT

Hi Stephen,

Any update or ETA on this? A customer wantd to use a DNS name in the source of a rule, such as "jsmith.dyndns.org" and have it resolve itself to an IP dynamically.

Thanks.

Re: Feature Request - DNS name as source/destination

swhyte — Wed, 17 Nov 2010 22:20:01 GMT

Hello,

your sales contact would be the best resource for tracking on a feature request that you submitted.

But regarding this feature, it will be in our NICE release which is scheduled to be available by the beginning of 2011.

thanks,

Stephen