Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Cvr
Explorer
Jump to solution

Asterisk Usage in Creating Domain Object

Hello All,

 

While creating Domain object in MDSM, Can I add Asterisk symbol in front of domain.  If I add will it work in rules?

 

Example: 

Object Name:  .*.powerbi.com

 

Thanks,

Rajesh.

0 Kudos
2 Solutions

Accepted Solutions
Lesley
Leader Leader
Leader

No you cannot use * for both options. So if you enable FQDN or disable it you have to work with a dot (.) not with *

  • Select FQDN

    In the object name, use the Fully Qualified Domain Name (FQDN). Use the format . x.y.z (with a dot "." before the FQDN). For example, if you use . www.example.com then the Gateway matches www.example.com

    This option is supported for R80.10 and higher, and is the default. It is more accurate and faster than the non-FQDN option.

The Security Gateway looks up the FQDN with a direct DNS query, and uses the result in the Rule Base

This option supports SecureXL

 Accept templates. Using domain objects with this option in a rule has no effect on the performance of the rule, or of the rules that come after it.

  • Clear FQDN

This option enforces the domain and its sub-domains. In the object name, use the format . x.y for the name. For example, use . example.com or . example.co.uk for the name. If you use . example.com, then the Gateway matches www.example.com and support.example.com

The Gateway does the name resolution using DNS reverse lookups, which can be inaccurate. The Gateway uses the result in the Rule Base, and caches the result to use again.

-------
If you like this post please give a thumbs up(kudo)! 🙂

View solution in original post

the_rock
Legend
Legend
4 Replies
Lesley
Leader Leader
Leader

No you cannot use * for both options. So if you enable FQDN or disable it you have to work with a dot (.) not with *

  • Select FQDN

    In the object name, use the Fully Qualified Domain Name (FQDN). Use the format . x.y.z (with a dot "." before the FQDN). For example, if you use . www.example.com then the Gateway matches www.example.com

    This option is supported for R80.10 and higher, and is the default. It is more accurate and faster than the non-FQDN option.

The Security Gateway looks up the FQDN with a direct DNS query, and uses the result in the Rule Base

This option supports SecureXL

 Accept templates. Using domain objects with this option in a rule has no effect on the performance of the rule, or of the rules that come after it.

  • Clear FQDN

This option enforces the domain and its sub-domains. In the object name, use the format . x.y for the name. For example, use . example.com or . example.co.uk for the name. If you use . example.com, then the Gateway matches www.example.com and support.example.com

The Gateway does the name resolution using DNS reverse lookups, which can be inaccurate. The Gateway uses the result in the Rule Base, and caches the result to use again.

-------
If you like this post please give a thumbs up(kudo)! 🙂
the_rock
Legend
Legend

I have not tested that in some time, but it has to start with a . sign.

Andy

the_rock
Legend
Legend
the_rock
Legend
Legend

Also, for the context, that option for fqdn also matters, depending on exactly what you are accessing @Cvr 

Andy

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events