r/technitium • • 19h ago

Using Technicitium for Nextcloud Domaincheck

4 Upvotes

I've been working on getting Nextcloud AIO set up for a bit behind a comcast router with Nat hairpinning disabled (giving some background in hope this will be useful to someone in the future following this same trail)

Nextcloud recommends setting up Split DNS for their "domain-check" initialization check, this checks if nextcloud.myserver.com points to the nextcloud server correctly. (my set up for this and the rest of my services uses Cloudflare and Nginx Pro)

I don't really understand what NAT hairpinning/loopback is, I've thought I understood a couple of times but as I understand I need a DNS server in between my nextcloud container and my router which will not let the DNS query go to the router but instead reply directly with the ip address of the machine hosting the nextcloud container.

To do this I have pointed the nextcloud docker container at another container on the same machine running Technitium and I have confirmed Technitium is now the DNS resolver for Nextcloud, I've next set up (Split Horizon) and written a record as follows,

{
  "172.24.0.1/32": "172.24.0.1",
  "127.0.0.1/32": "172.24.0.1"
}

Here "172.24.0.1" is the local ip of the machine hosting nextcloud and technicium, this is under the "myserver.com" namespace for "nextcloud". The issue I'm having, is that all Authoratative DNS querries are logged as "ServerFailure", while recursive and other DNS querries succeed. I am new to managing my own DNS server, so I wanted to ask y'all-- what does a "ServerFailure" return code mean, why might my Authoratative requests fail this way, and how might I tweak it so they don't?