About this Image :

Docker Hub : https://hub.docker.com/r/marioyhzkiel/glorydns-node
glorydns-node:1.1 is a GloryDNS Node version that can be installed locally. Once this Docker container is running, the node will request a connection to GloryDNS Master until approved, allowing it to participate in the network.

GloryDNS-Node Features & Capabilities
GloryDNS-Node is an image Docker for running DNS-based content filtering and analytics on a local server. Node configuration is available via the web GUI with 10 built-in rule policies.

• Mode protection: No Protection, Malware Protection, Ads Protection, Family Protection, or a combination
• Filter domains with wildcard, applications, websites, or games
• Filter content categories (social media, messaging apps, etc.)
• Filter TLDs (.com, .org, .net, etc.)
• Configure NXDOMAIN redirect, YouTube Restricted Mode, and SafeSearch enforcement
• Query log & analytics dashboard, exportable to XLS/CSV

Distributed Cache Resolver Cluster Technology

• GloryDNS-Node uses a Distributed Cache Resolver Cluster to provide content filtering and analytics.
• Each node forms part of a large cluster network and acts as a resolver for its own users, while also serving queries from other connected nodes. It stores DNS cache locally from its own user queries and from other nodes.
• If a query is not found in the local cache, it is forwarded to a centralized system that distributes the query to other nodes in the cluster using load balancing:
  • 40% based on RTT and health check
  • 40% randomly among healthy nodes
  • 10% based on round-robin
• Resolved queries are stored as cache in the selected cluster resolver node, then returned to the requesting node and stored in its local cache.
• This mechanism distributes DNS cache across many nodes. Users can access both their own cache and cache from other nodes, improving resolution speed and efficiency. Queries from one user can benefit other users across the cluster.

Notes

• Running a node means participating in the GloryDNS DNS distributed cache cluster.
• Nodes can be restricted or rejected if suspicious activity is detected, such as flooding or script manipulation.