diff options
| -rw-r--r-- | articles/2023-02-13-new-website-using-gnix.md | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/articles/2023-02-13-new-website-using-gnix.md b/articles/2023-02-13-new-website-using-gnix.md index c919ad7..04cdc02 100644 --- a/articles/2023-02-13-new-website-using-gnix.md +++ b/articles/2023-02-13-new-website-using-gnix.md @@ -49,13 +49,14 @@ previously. At this point I started rewriting my main website. Another inconvinience was that I would need `certbot` to aquire one certificate for each subdomain. Letsencrypt offers wildcard certificates; These can be -obtained by solving a ACME challenge that requires changing DNS record (to prove -you own the domain). My current registrar (Namecheap) does not offer me an API -for automatically applying these though. They do however (through a very very -confusing, badly designed user interface) allow me to set a custom nameserver. -By setting the nameserver to `144.91.114.82` (IP address of my VPS) the server -can run its own nameserver that has authority over resolving `metamuffin.org`. I -used BIND9's `named` to do that and also dynamically update records. +obtained by solving an ACME challenge that requires changing a DNS record (to +prove you own the domain). My current registrar (Namecheap) does not offer me an +API for automatically applying these though. They do however (through a very +very confusing, badly designed user interface) allow me to set a custom +nameserver. By setting the nameserver to `144.91.114.82` (IP address of my VPS) +the server can run its own nameserver that has authority over resolving +`metamuffin.org`. I used BIND9's `named` to do that and also dynamically update +records. ```conf # /etc/named.conf (-rw-------; owned by named) |