Technical Tip: How to allow a website that is being blocked by a DNS Filter
| Description | This article describes configuring a DNS Filter profile to allow a website that is blocked by the DNS Filter. |
| Scope | FortiGate. |
| Solution | In some cases, websites are blocked by a DNS Filter even though the category is set to Allow. Example 1:
The category to which the https://accounts.o2.co.uk/ website belongs is allowed in the DNS Filter. However, the website still gets blocked.
C:\Users>nslookup accounts.o2.co.uk Name: d3c17wgn4zp1k7.cloudfront.net Addresses: 18.172.153.90 18.172.153.59 18.172.153.12 18.172.153.33 Aliases: accounts.o2.co.uk lbprdcachetieraccountsproxy.o2r53ctp.co.uk lbprd0cachetieraccountsproxy.o2r53ctp.co.uk
Note: Adding only 'accounts.o2.co.uk' is not sufficient.
Example 2:
https://login.bornemann.net is blocked by the DNS Filter profile.
C:\Users\>nslookup login.bornemann.net Non-authoritative answer: Name: openresty-prod.boag-backend.net Address: 185.39.176.42 Aliases: login.bornemann.net
openresty-prod.boag-backend.net should also be added in the DNS Filter profile in order to have access to login.bornemann.net.
|
