I think the lack of an SOA record means I can't point down at this subdomain from my domain...
ahab is the host running coredns_omada in docker.
in my primary domain's config I have:
dyn IN NS ahab.example.com.
And DNS resolution directly works fine:
$ dig @ahab.example.com wificlient.dyn.example.com +short
192.168.1.90
$
but there's no SOA record for dyn.example.com from the coredns server:
$ dig @ahab.example.com dyn.example.com soa
; <<>> DiG 9.18.30-0ubuntu0.20.04.2-Ubuntu <<>> @ahab.example.com dyn.example.com soa
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 58853
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 22 (No Reachable Authority): (at delegation dyn.example.com.)
;; QUESTION SECTION:
;dyn.example.com. IN SOA
;; Query time: 23 msec
;; SERVER: 192.168.1.61#53(ahab.example.com) (UDP)
;; WHEN: Thu Aug 28 10:21:28 CDT 2025
;; MSG SIZE rcvd: 74
$
and the Corefile:
. {
health :8080
omada {
controller_url {$OMADA_URL}
site {$OMADA_SITE}
username {$OMADA_USERNAME}
password {$OMADA_PASSWORD}
refresh_minutes 1
}
forward . {$UPSTREAM_DNS}
debug
}
How do i get an SOA for the domains created by this plugin?
I think the lack of an SOA record means I can't point down at this subdomain from my domain...
ahabis the host running coredns_omada in docker.in my primary domain's config I have:
And DNS resolution directly works fine:
but there's no SOA record for dyn.example.com from the coredns server:
and the Corefile:
How do i get an SOA for the domains created by this plugin?