ref: db5ac4f95380f44eb3268570160689f57fb5471c
parent: a07c0253517823ec040efa22bdb2934fce85cd1f
author: jrmu <jrmu@cloud9p.org>
date: Sun Aug 4 19:17:18 EDT 2024
Added sample ndb config and replaced specific IPs with generic values
--- a/ndb.ms
+++ b/ndb.ms
@@ -1,4 +1,4 @@
-Note the differences in how the addresses must be formatted:
+Note the differences in how the addresses must be formatted:
.P1
; ndb/csquery
@@ -24,4 +24,32 @@
.PP
Be aware that you must include -L to prevent users outside the local network from being able to turn your caching server into an open relay for denial of service amplification attacks. -L provides a crude form of access control. Otherwise, you must firewall off access to prevent becoming an attack vector.
+You will want to add your records to /lib/ndb/local, similar to the following:
+
+sys=example.com ether=f2b2b3daeb89 ip=198.51.100.2 ipmask=255.255.255.0 ipgw=198.51.100.1
+ ntp=pool.ntp.org
+ dns=198.51.100.1
+
+dom=example.com soa=
+ refresh=300 ttl=300
+ ns=ns1.example.com
+ ns=ns2.example.com
+ ip=198.51.100.2
+ dnsslave=ns2.example.com
+ mb=postmaster@example.com
+ mx=mail.example.com pref=5
+ txt="v=spf1 mx -all"
+
+sys=ns1 dom=ns1.example.com ip=198.51.100.2
+sys=ns2 dom=ns2.example.com ip=198.51.100.2
+sys=mail dom=mail.example.com ip=198.51.100.2
+sys=_dmarc dom=_dmarc.example.com txt="v=DMARC1; p=none"
+
+dom=2.100.51.198.in-addr.arpa soa=
+ refresh=300 ttl=300
+ ns=ns1.example.com
+ ns=ns2.example.com
+
+
+Replace 198.51.100.1, 198.51.100.2, example.com, and postmaster@example.com with your actual values.