marioyhzkiel/glorydns-node repository overview

⁠GloryDNS Node

GloryDNS | Threat Protection & Content Filtering in Web Base With DNS-Layer Security

New firewall for your network with our Dynamic Recursive DNS & DNS-layer security.

Filter or unfilter domains (with or without all subdomains), websites, applications, games, or content by category. Enable or disable SafeSearch and NXDOMAIN redirection as you like via the content filtering web GUI. Configure it easily on your home or office network router with GloryDNS.

⁠About this Image

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.

By running a GloryDNS Node, you are ready to contribute to the distribution of GloryDNS DNS queries in a large cluster 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:
  • 70% based on RTT and health check
  • 20% 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.

⁠GloryDNS Node WEB GUI Default Username & Password

Username:

glorydns

Password:

glory#dns!

⁠Step 1: Pull the Image

docker pull marioyhzkiel/glorydns-node:1.1

or

docker pull marioyhzkiel/glorydns-node:latest

⁠Step 2: Stop and disable the local systemd-resolved service

So you can expose UDP port 53 from the Docker container to your host.

sudo systemctl stop systemd-resolved
sudo systemctl disable systemd-resolved

⁠Step 3: Run the Container

docker run -d --name glorydns-node \
-p 53:53/udp \
-p 53:53/tcp \
-p 80:80 \
--cap-add=NET_ADMIN \
--sysctl="net.ipv4.ip_forward=1" \
-e HOST_IP="$(hostname -I | awk '{print $1}')" \
--restart unless-stopped \
marioyhzkiel/glorydns-node:1.1

or

docker run -d --name glorydns-node \
-p 53:53/udp \
-p 53:53/tcp \
-p 80:80 \
--cap-add=NET_ADMIN \
--sysctl="net.ipv4.ip_forward=1" \
-e HOST_IP="$(hostname -I | awk '{print $1}')" \
--restart unless-stopped \
marioyhzkiel/glorydns-node:latest

⁠Ports explanation:

• 53 TCP/UDP → DNS service
• 80 TCP → Web GUI

Notes:

• Container runs with NET_ADMIN capability to manage IP internally.
• supervisord manages all services inside the container.

⁠Step 4: Check the Container

docker ps
docker logs glorydns-node

⁠Tips

• Use the 1.1 tag for this stable version.
• Update the image by rebuilding from the Dockerfile if there are patches or upgrades.
• Scan the image regularly for vulnerabilities using tools like trivy or docker scan.