We describe how to run our pre-built executable within a docker
container. They can figure out the rest from there.
If they don't understand those instructions, they shouldn't be running
their own DNS server.
ns-vultr.nono.io is a bad nameserver because it's shut down for ~8 days
each month (when the unbelievable Singapore hunger for NTP uses up my
monthly allowance of 3TB)
Besides, three nameservers is enough.
We now introduce a second Dockerfile, `Dockerfile-nginx`, to be used for
the web assets for sslip.io.
It does not run TLS; we assume that the load balancer will take care of
that.
We also gussied-up the PowerDNS Dockerfile with minor changes.
- nodePort service is merely a proof-of-concept; this won't be the final
form the service takes. The port needs to be 53, not 32767.
- the deployment doesn't include the nginx webserver, merely the DNS
server. Also, I had trouble connecting both UDP & TCP to port 53,
so I chose UDP.
- Include BIND secondaries for nono.io/nono.com
(use this & you'll be unwitting secondaries for my domains)
- Fedora-based. Because IBM/Red Hat hires a lot of the Linux kernel developers.
