node: id: mono-node-1 role: primary listen: 0.0.0.0:53 database: type: boltdb path: /var/lib/ns1/mono.db
Have you tried running NS1 in mono mode? Let us know in the comments what filters or automation you’re testing. ns1 mono
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): node: id: mono-node-1 role: primary listen: 0
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 | Load a zone via the API (single node
api: enabled: true listen: 127.0.0.1:8080
Deploying NS1 in Mono Mode: A Lightweight DNS Powerhouse