Synet DNS

Overview

Synet DNS provides centralized domain and IP management for services requiring stable, resolvable identities within the Synet network.

It is intentionally separated from decentralized publishing (synet-cli) and is used for enterprise-grade, persistent, and auditable infrastructure — including .sy and .synet domains, static IPs, and custom nameservers.

Package Breakdown

Synet DNS consists of two distinct components:

synet-dns — CLI Tool
Manages .sy domain registration, IP reservations, and DNS records.
synet-dns-server — DNS Server
Hosts actual DNS zones, resolves .sy domains, and syncs with Synet Root.

Key Roles

Package	Role
`synet-dns`	Client-side CLI for managing domains and requesting static IPs.
`synet-dns-server`	Authoritative nameserver hosting `.sy` zones.
`synet-gateway`	Enforces IP allocation, handles pool management.

Example Use Cases

Registering company.synet domain to point to a static service IP.
Running a private .synet nameserver synced to Synet Root.
Reserving static IPs for core infrastructure.
Renewing or deleting domain records.

Core Commands

# Register a domain
synet-dns register-domain --name myapp.sy --ns ns1.myapp.sy --ip fd00:1::100

# Add DNS record
synet-dns add-record --domain myapp.sy --type AAAA --ip fd00:1::100

# Request static IP
synet-dns request-static-ip --name myapp.sy --gateway synet.mit.edu

Domain Management Features

Command	Purpose
`register-domain`	Register a new `.sy` domain and point to a nameserver.
`add-record`, `update-record`, `delete-record`	Modify DNS records (AAAA, CNAME, NS, etc.).
`list`	List all records for a domain.
`renew`	Extend domain registration.
`resolve`	Lookup domain or ID (centralized or decentralized).

Static IP Allocation Flow

Request IP:

synet-dns request-static-ip --name myservice.sy --pubkey 0xABC... --gateway synet.mit.edu

Gateway verifies public key, assigns IP:

Success: Assigned fd00:ffff::10

IP is tied to identity and can be verified across Synet.

Server Setup (`synet-dns-server`)

This runs a DNS server for a .sy zone:

synet-dns-server --domain myapp.sy --root-registry registry.synet.sy --proxy

Config File Example:

domains:
  - name: myapp.sy
    records:
      - type: AAAA
        ip: fd00:1::100
    proxy: true  # Hide backend IPs

Features:

Root registry sync for NS validation.
Proxy mode (hide real IPs from responses).
Can be run per-service, per-org, or globally.

Design Philosophy

Principle	Implementation
Decentralized/centralized separation	`synet-cli` = for agents, `synet-dns` = for operators
Security	Static IPs tied to keys; all writes require authorization
Modularity	`synet-dns-server` can be swapped or extended

Architecture Diagram

flowchart TD
    A[Agent or Service Provider]
    B[Synet Root Registry]
    C[DNS Server]
    D[Client Agent]
    A -->|register-domain| B
    B -->|NS record sync| C
    D -->|resolves domain| C

Future Roadmap

DNSSEC support (signed zones).
Auto-renewal hooks via SPM.

Summary

The Synet DNS stack is designed for:

Agents needing stable, resolvable identities.
Enterprises requiring .sy zone control.
Gateways issuing permanent IPs.

This is not for dynamic or DHT-based publishing — use synet-cli for that.

Join Dev

Synet Dev Portal

Learn More

Synet CLI
Synet Gateway

:: synet-dns