For allowing or denying a specific site or service, we recommend the use of IPv4 Allowed and Denied Lists. As networking technologies have shifted in recent years, it has become more difficult to leverage Domain Allowed and Denied Lists effectively as we will explain in this article.
Domain blocking does not block IPs or stop IP connections from going through. It intercepts the DNS request to look up a domain name. It is important to note, when encrypted DNS is enabled, the ThreatBlockr is unable to see the the domain name in the DNS request. Due to this, the ThreatBlockr is unable to allow or deny any Domains when encrypted DNS is enabled.
Domain Denied Lists
Once a domain has been looked up, if the domain is not on a denied list, it allowed the DNS request to proceed to the original destination server. If the domain is on a denied list, then the Bandura Cyber ThreatBlockr will return a NX domain, a non-existent domain response to the user to prevent their application from continuing to connect to the blocked domain.
If you add the domain to the denied list and that DNS request has already been cached by an internal DNS server, then the ThreatBlockr will not see the outbound DNS request as it is being handled by the internal server. When adding a domain to the denied list, it is recommended to flush cache on the internal DNS server.
Domain Allowed Lists
Domain Allowed Lists are used to override blocks that may have occurred due to a Domain being on a Domain Denied List. As the ThreatBlockr does not perform a namespace lookup, and as IP connections are not blocked or stopped by domain blocking, a Domain Allowed List entry will not allow an IP that has been identified by a Threat List or Denied List.