Once you have everything filled out click the Save button at the bottom-right. Name the Object whatever you like and add the FQDN in the FQDN Hostmane field. In this case it was an external website so the Zone will be WAN.
In this case I logged into the SonicWall’s web interface and navigated to Object > Match Objects > Addresses > Address Objects.Ĭlick the +Add button at the top to add a new Address Object.Ĭhange the Zone Assignment to the correct option. You need to create Objects and then those objects are applied to rules or policies. One I received the approvals I could make the changes. In this instance I sought approval from our contact at this client as well as following our internal Change Management process by creating an RFC and getting it approved before applying any changes. You should always seek approval following your internal policies before making any changes. We won’t get into why the client needed to access this website but there was a legitimate reason for them to be accessing it. In this instance the URL was for the PA state lottery and it was being blocked because it is categorized as gambling. It did not load and gave the below error message telling me that it was being blocked by the SonicWall. I then connected to, in this case, the customers server and attempted to access the same website there. This told me that the address was correct and that the website was not down or otherwise having issues. In this instance I checked to see if I was able to access the website from my computer first. To start, you should always ensure that the website is actually being blocked by the SonicWall and there isn’t something else going on. I was not able to find a document that clearly outlined the process so I figured that this would be a great time for a blog post! I recently had to whitelist a website for a client that is using a SonicWall Firewall running SonicOS 7.0.