Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
roc-dns [2020/10/29 08:35] rafi |
roc-dns [2021/03/09 11:55] rafi |
||
---|---|---|---|
Line 1: | Line 1: | ||
==== Managing ROC-DNS ==== | ==== Managing ROC-DNS ==== | ||
- | To get access to ROC-DNS, you must provision a ROC and then login to the Threat Detection dashboard. | + | To get access to ROC-DNS, you must provision a ROC and then login to the Threat Detection dashboard. |
Our enterprise level ROC-DNS is based on state of the art threat detection to ensure that your endpoints are protected. It uses its threat algorithm analysis to block malicious or suspicious domains. It is made up of a combination of opensource and proprietary solutions. | Our enterprise level ROC-DNS is based on state of the art threat detection to ensure that your endpoints are protected. It uses its threat algorithm analysis to block malicious or suspicious domains. It is made up of a combination of opensource and proprietary solutions. | ||
Line 46: | Line 46: | ||
=== DNS Filtering when using Active Directory on LAN === | === DNS Filtering when using Active Directory on LAN === | ||
- | You can use Privatise DNS filtering in conjunction with your Active Directory on the local network. | + | You can use Privatise DNS filtering in conjunction with your Active Directory on the local network. |
+ | === Custom Fully Qualified Domain Names === | ||
+ | |||
+ | You can attach Fully Qualified Domain Names to an individual IP if it's static. To do so: | ||
+ | |||
+ | 1. Go to Local DNS Records | ||
+ | |||
+ | 2. Add a Fully Qualified Domain Name on the left, and static IP of the Privatise agent you want to connect to. | ||
+ | |||
+ | 3. Alternatively, | ||
+ | |||
+ | {{:: | ||