DNS and .vonet Domains

This page outlines how DNS will work within the VONet network and the future use of a `.vonet` Top-Level Domain (TLD) for community-hosted services. This system is currently in planning and not yet active.

Overview

As part of the VONet network, we are planning to deploy an internal DNS system that supports a custom TLD: `.vonet`.

Once live, users connected to the VONet mesh will be able to access local services by name using domains like:

example.vonet

Outside the mesh, those services (if configured for public access) will be reachable via:

example.dns.vonet.org

This will provide a consistent and flexible way to host and access services from both inside and outside the network.

Official Function Addresses

• https://vonet.org/ – Main VONet website.
• https://m.vonet.org/ – PWA Mobile app for iPhone and Android.
• https://wiki.vonet.org/ – Knowledge base and documentation.
• https://support.vonet.org/ – Help and support ticket system.
• https://forums.vonet.org/ – Community discussion boards.
• https://cloud.vonet.org/ – Storage, messaging, and planning tools.
• https://data.vonet.org/ – Signups, setup, volunteer scheduling, Relations Management, Event planning and management, and service calls.
• https://newsletter.vonet.org/ – Email newsletter platform.
• https://status.vonet.org/ - Network and System outage notification system.

Planned DNS System

The VONet DNS servers will act as their own internal root, designed to:

• Resolve `.vonet` domains locally across the mesh
• Handle standard internet domains by pulling from external root DNS servers
• Provide fast, decentralized resolution for mesh users

Using the VONet DNS will be optional. Users will still be able to use public resolvers like:

• `8.8.8.8` (Google)
• `1.1.1.1` (Cloudflare)

However, VONet's DNS will offer a key benefit: If there is a large-scale internet outage, users on the mesh will still be able to access local `.vonet` services without relying on the broader internet.

Domain Registration (Planned)

We intend to allow VONet participants to register `.vonet` subdomains for personal or community use. These domains will point to services hosted on the mesh and, optionally, through a public-facing gateway for outside access.

Registration will involve:

1. Connecting to the mesh
2. Choosing a domain name (e.g. `yourname.vonet`)
3. Sending a request with:

• Your chosen name
• A brief description of your service
• Your node’s IP or mesh location
• Whether you want external access (via `yourname.dns.vonet.org`)

Registration will be manual at first and may move to an automated request tool later.

Use Cases

Some possible use cases for `.vonet` domains:

• Personal websites on the mesh
• Community tools or directories
• Mesh-only apps or services
• Local chat, games, or file sharing
• Projects run by nonprofits or educators

Technical Planning Notes

• VONet DNS will be authoritative for `.vonet` inside the mesh
• DNS traffic will be handled locally when possible to improve performance and reliability
• Split DNS is planned so names resolve differently inside and outside the network
• Mesh users will be encouraged to use VONet DNS for resilience and local access

Important Notes

• This system is still in planning and is not yet operational
• Any example domains or links are for illustration only
• More information will be provided as development progresses

Questions or Feedback?

If you have ideas, questions, or want to help with DNS planning, please reach out: Email: support@vonet.org Forum: https://forum.vonet.org