Because it’s mono, no peer addresses or consensus raft configuration is required. Load a zone via the API (single node means no replication lag):
When we talk about NS1, most people think of massive, globally distributed DNS filtering, traffic steering, and real-time analytics. But what about a mono (single-node) deployment? Whether you’re building a staging environment, a low-budget authoritative DNS server, or simply testing NS1’s powerful API-driven rules, running NS1 in mono mode is a viable, often overlooked option. ns1 mono
Have you tried running NS1 in mono mode? Let us know in the comments what filters or automation you’re testing. Because it’s mono, no peer addresses or consensus
curl -X PUT -H "X-NS1-Key: your-api-key" \ -d '"answers": ["answer": ["192.0.2.1"], "answer": ["192.0.2.2"]], "filters": ["weighted"]' \ http://localhost:8080/v1/zones/example.com/www The mono node will evaluate filters locally and return the best answer per request. | Feature | Mono behavior | |---------|----------------| | High availability | None | | Data replication | N/A | | Analytics aggregation | Local only | | DDoS protection | Single point of attack | | Rolling upgrades | Downtime required | curl -X PUT -H "X-NS1-Key: your-api-key" \ -d
api: enabled: true listen: 127.0.0.1:8080
Deploying NS1 in Mono Mode: A Lightweight DNS Powerhouse
❌ Not for production where downtime of a single node would cause outage. Assuming you have access to NS1’s on‑prem software or a compatible open‑core build, a minimal ns1.conf might look like: