topic Re: Allowing TCP/UDP ports (not http/https) to a FQDN or CNAME of a website in General Topics

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

Jonathan_Diegan — Fri, 06 Sep 2019 12:57:22 GMT

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.

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

PhoneBoy — Fri, 06 Sep 2019 18:46:27 GMT

An FQDN domain object what is required here.

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

Jonathan_Diegan — Fri, 06 Sep 2019 18:51:43 GMT

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

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

PhoneBoy — Fri, 06 Sep 2019 19:25:07 GMT

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.