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

Allowing TCP/UDP ports (not http/https) to a FQDN or CNAME of a website

Hopefully an easy one. What is the best way to allow TCP/UDP ports (not HTTP/https) to an FQDN or CNAME of a website in R80.30? Setup a Domain object in an access policy (Con being that the whole domain needs to be added)? URL/APP filtering (How is this done with a TCP/UDP port other than 80/443)?  For URL/APP does Https offloading need enabled? Something else I am missing? In other vendor devices, adding this seems fairly easy, it seems a bit more involved in Checkpoint. 

0 Kudos
1 Solution

Accepted Solutions
PhoneBoy
Admin
Admin
An FQDN domain object refers to a single FQDN hostname only.
If you want to connect to www.site.domain.com, you create an FQDN domain object with the name .www.site.domain.com.

View solution in original post

3 Replies
PhoneBoy
Admin
Admin
An FQDN domain object what is required here.
Jonathan_Diegan
Participant

So would Http(s)://www.site.domain.com translate to FQDN .site.domain.com?

0 Kudos
PhoneBoy
Admin
Admin
An FQDN domain object refers to a single FQDN hostname only.
If you want to connect to www.site.domain.com, you create an FQDN domain object with the name .www.site.domain.com.

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events