This project is not covered by Drupal’s security advisory policy.
Overview
Private DNS is a self-hosted dynamic DNS module for Drupal that enables you to access machines with dynamic IP addresses using consistent hostnames, without relying on third-party services.
Use Cases
- Remote access to office computers from home with dynamic IP connections
- Development servers behind dynamic public IPs - grant access to testers without buying additional hosting
- Direct access to IoT devices (web cameras, automation systems) without routing through external servers
- Privacy-conscious users who don't want to share network info with public DNS services
How to Use
- Install the module (Composer recommended:
composer require drupal/private_dns) - Generate unique keys for each machine from Configuration > Private DNS
- Download and configure the provided client scripts
- Set up cron jobs to run scripts periodically on each client machine
Features
- Self-hosted - full control over your DNS data
- No recurring costs - free alternative to commercial services
- Privacy-focused - keep your network information private
- Included client scripts with backup, validation, and logging
- Multiple domain aliases support per host
Requirements
- Drupal 9.4 or 10.2+ or 11.0+
- Client machines: Bash 4.0+, wget, ping, root/sudo access
Documentation & Support
See the project page and issue queue for documentation and support.
Supporting organizations:
created the module
Project information
- Project categories: Developer tools
10 sites report using this module- Created by afagioli on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
