About TravisC

The URL is defined by website. In the case of an HTTP request to 'sega.com', the website responds with a 301 (Permanently Moved) to 'www.sega.com'. If you are using Chrome, it will hide the 'www.', but if you click on it will show it. If you use Firefox, you will see that you put in 'sega.com' and then it is changed to 'www.sega.com'. You can use Developer tools on either browser to see what the URL should be by following the request URL.   The firewall doesn't attempt to do a reverse DNS lookup on URL categories. The URL is determined by looking by looking at the HTTP headers, the SSL Client Hello SNI, and SSL Server Hello  Common Name (CN) of the Server Certificate Subject DN. This behavior changes if SSL decryption is used.   https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClzlCAC ... View more

Hello and thanks for your answer. You have put me in the right direction. Luckily we don't use the 192.168.0.0/24 range in our /16 subnet. So I was able to solve the problem via NAT and route without another Linux VM. But for the solution I needed another virtual router. I can' t bind the 192.168.99.1 interface to the default router because its subnet is already bound to the 192.168.100.15/16 interface. The following picture should explain my solution: Thanks a lot! ... View more