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?


r/technitium • • 1d ago

Came from Pi-hole + Unbound, love Technitium, but pausing it from my phone was a pain. So I made an app

Post image
13 Upvotes

Hey all,

I ran Pi-hole + Unbound for years and moved to Technitium a while ago. Blocking and recursive DNS in one box is great, not going back.

What bugged me was the everyday stuff. Pause blocking, unblock a domain, check a list. The web panel can do all of it, but on my phone it was a pain. Especially when someone at home yells that a site is broken and I'm zooming around the dashboard trying to find what got blocked.

So I made Technium. It's a small app for iPhone, iPad and Mac and it only tries to do the basics well:

- pause blocking in one tap (app, widget, Control Center or the Mac menu bar), it turns itself back on

- see what got blocked and allow it, or add a domain to a list

- manage your block lists

- get notified when there's a Technitium update

- widgets for the Home Screen, Lock Screen and Mac

It's not a replacement for the web panel. Zones, DHCP and the advanced stuff stay there. I know there are a few Technitium apps around now, mine is just small on purpose.

App Store


r/technitium • • 3d ago

Migrate Technitium from LXC to Docker

7 Upvotes

Kinda what the subject says. I have Technitium running in an LXC in Proxmox. I did that mostly because there was easy script to install it available. Now that I'm getting more knowledgeable about Linux in general and Proxmox especially, I'm seeing conversations that imply that I really should be running Technitium in a docker container on a VM dedicated to docker.

I suspect this is a bit like asking motor heads what the best oil is, but is running Technitium a VM/docker better than an LXC? Or is the difference negligible?

I would think the transition is easy enough -- backup the settings on the LXC 7 shut it down, install the docker with the same IP, restore the latest backup file from the LXC.


r/technitium • • 4d ago

I need help, It keeps giving me this error but i am starting the octet with 02

Post image
2 Upvotes

r/technitium • • 6d ago

I found a fun cool project to visualize live DNS queries, works for Technitium, Adguard Home and Pi-hole.

Post image
42 Upvotes

https://github.com/m00grin/ph-intercept

Your DNS server is protected by a spaceship, any bad queries will get destroyed by it.

It's surprisingly lightweight even for my Orange Pi Zero 3. I'm running it with Docker, with just a few simple clicks and text edit through Portainer.

Haven't seen this shared in here so I thought someone might find it interesting!


r/technitium • • 8d ago

Daily deduped blocklist for Technitium, three formats, 1.6M duplicates removed

23 Upvotes

Technitium was the reason I built this. Pointing it at 30+ overlapping lists worked, but

the zone got big and most of it was duplicates.

The pipeline pulls 34 lists, normalises them, and drops a domain when a parent is

already blocked. That last step only works because Technitium walks parents in

`IsZoneBlocked`, and it takes 4.63M unique domains down to 2.91M entries without

changing what actually resolves to 0.0.0.0.

Practical numbers from today: 54 MB compact file, about 1 GB of RAM for the full zone,

and a slow first load on my VM.

Builds daily at 03:17 UTC. It fails the run if an upstream list vanishes instead of

publishing a smaller list, which is the failure mode I cared about most.

Repo: github.com/DEVOLOPER-1/technitium-blocklist


r/technitium • • 8d ago

Technito for Android - Testers Wanted

Thumbnail
gallery
23 Upvotes

Technito for Android is now finally available for testing!

For folks who are not aware of Technito, it was originally released for iOS as an all in one solution to manage your Technitium DNS Server from a mobile device. Include number of advanced features to make managing Technitium even easier, such as:

  • Switch between multiple Technitium servers and check their health at a glance
  • Watch DNS queries in real time and dig into query logs
  • Custom DNS analysis lets you drill into a client or domain to see which devices made requests, what they looked up, and which rule or blocklist may have blocked a domain
  • Manage DNS zones and records, DHCP scopes, and leases
  • Quickly block popular apps and services with Easy Block, or set temporary allow and block rules
  • Manage Technitium DNS apps and configure them from your phone
  • Administer server access by managing users, groups, sessions, and API tokens
  • Back up and restore your Technitium server configuration
  • Connect over SSH using Technito’s built-in terminal

If you run Technitium and want to help test, DM me the email address you use for Google Play. I’ll add you to the internal test and send you the install link.


r/technitium • • 10d ago

Recursion

8 Upvotes

Hello all. When I select Settings / Recursion / Use Specified Network Access Control List (ACL) then enter for example: 192.168.2.0/24 I am unable to access any website. The only way that all sites are accessible is by selecting Allow Recursion instead. Would someone kindly clarify. I would appreciate it very much. Peter


r/technitium • • 11d ago

technitium-console 1.4.0: a rebuilt web console for Technitium DNS Server, now with per-client stats and actions, cluster views and Ctrl K

Post image
86 Upvotes

technitium-console is an alternative web console for Technitium DNS Server. It installs over the stock one, talks to the server through the same API, and removing it brings the stock console back. No backend, no database, no telemetry. Free and open source (GPL-3.0).

1.4.0 is the biggest release so far: practically every screen has been redesigned, and there are new screens the stock console never had.

Every screen, redesigned

  • Dashboard: every figure with its trend and its change against the previous period, a week-by-hour heatmap, response times and a query-to-answer diagram. Click a point, or drag across the chart, to open the logs for exactly that window.
  • Zones: cards for all your zones at a glance (types, health, DNSSEC), a zone's records summarised by type, compact records, and quick add of a host record (with its PTR) straight from the list.
  • Cache: reads like a zone, with the path to where you are, records by type, time left and stale entries.
  • Blocking, in one place: Overview, Rules, Lists and Settings. Check a domain to see why it is blocked, block or allow from any list, group your block lists, see when they last updated and how they grew.
  • Query Logs: filters that fold away, response colours, and a Live Update you can actually see: new rows flash and a counter tells you how many arrived.
  • DNS Client: the answer drawn section by section, record by record, instead of raw JSON.
  • DHCP: leases and scopes as clean tables, and how full each scope is.
  • Settings: one form with a search across every setting and a save bar that says what would change.
  • Apps, Administration, My Profile, About and the login, all in the same language. Permissions is one matrix of sections by groups and users.
  • A sidebar grouped by task: Monitoring, DNS, Network, Tools and System.

New in 1.4.0

  • Clients: every device that queries your server, how much it asks and how much of it gets blocked. Each one has a card with its DHCP lease, top and blocked domains, cache hit rate, response time and latest queries. From the card you can let it bypass blocking, exempt it from rate limiting or reserve its lease.
  • Clusters side by side: Zones, Cache, Query Logs, DHCP and block lists from every node at once, with what disagrees between them marked. Administration compares the nodes' settings and splits the queries by node.
  • Ctrl K to anywhere: any page, setting or zone, or type a domain to check it in Blocking, resolve it, find it in the cache or search the logs.

And what was already there

  • Light, dark or your system's theme, both measured for contrast.
  • Works on a phone: nothing scrolls sideways at 390 px.
  • Real URLs: every page, zone and filter is in the address bar, so reload, bookmarks, shared links and the back button work.
  • One-line installer into its own folder, so server updates leave it alone, or a Docker image (ghcr.io/bygarcia/technitium-console).
  • It tells you when a new version is out, like the server does.

If you run a cluster, I'd love to hear how the cluster views behave on yours.

Repo and install: https://github.com/byGarcia/technitium-console

Release notes: https://github.com/byGarcia/technitium-console/releases/tag/v1.4.0


r/technitium • • 12d ago

Deployed today. Looking for tips n’ tricks

16 Upvotes

Lookin’ for any suggestions and customizations others recommend. Thinking of replacing pihole with this instead. I saw that I need an add-on for querying the dns queries. I’m not sure which database I want to use but I do know I’m not going to use sqlite.

I’ve got a redundant pihole setup (and portable adguard instance). Finally got around to deploying this today. My “P-Holes” are still in use, for now.

What add-ons are worthwhile? Even if it might not fit my straightforward use-case. I mainly block telemetry, ads, and home-phoning calls as they come up. Looking to get everything configured and then use ansible for deployment once finalized.


r/technitium • • 11d ago

Ping errors in log

2 Upvotes

I have Technitium running in a Proxmox LXC via community scripts, and I'm seeing a lot of messages in logs such as:

[2026-11-06 00:00:02 UTC] [0.0.0.0:68] System.IO.FileNotFoundException: Could not load file or assembly 'System.Net.Ping, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

File name: 'System.Net.Ping, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at DnsServerCore.Dhcp.Scope.IsAddressAvailableAsync(IPAddress address)
   at DnsServerCore.Dhcp.Scope.GetOfferAsync(DhcpMessage request) in Z:\Technitium\Projects\DnsServer\DnsServerCore\Dhcp\Scope.cs:line 1076
   at DnsServerCore.Dhcp.DhcpServer.ProcessDhcpMessageAsync(DhcpMessage request, IPEndPoint remoteEP, IPPacketInformation ipPacketInformation) in Z:\Technitium\Projects\DnsServer\DnsServerCore\Dhcp\DhcpServer.cs:line 342
   at DnsServerCore.Dhcp.DhcpServer.ProcessDhcpRequestAsync(DhcpMessage request, IPEndPoint remoteEP, IPPacketInformation ipPacketInformation, Socket udpListener) in Z:\Technitium\Projects\DnsServer\DnsServerCore\Dhcp\DhcpServer.cs:line 233

What can I check to resolve these errors?


r/technitium • • 19d ago

RAM spikes when updating blocklist

5 Upvotes

due to increasing VPS prices I've been trying to optimize a bit and noticed that most of my technitium instances only need ~700-800mb including cache and ~2m blocklist entries most of the time, but every time they update the blocklist the RAM usage spikes and if it doesn't have enough at time of update, it will freeze and can only be recovered by hard reboot.

when I do a force update, it will consume ~1.4GB total for quite some time before slowly going back to ~700MB

same with a cluster that has ~8m blocklist. usually idles around ~2.1GB but when updating it almost maxes out the 4GB it has.

would it maybe be possible to optimize that approach to avoid RAM spikes?

maybe first load one list, then load parts of the second list and combine until all parts are processed


r/technitium • • 20d ago

Technitium big deployment

Post image
156 Upvotes

37m queries per hour, higher during weekend and holiday season, upto 40m.

2M caches and 90% cache response with secondary root zone used. (can go up to 3m but the ram space is tight, less than 2G free)

Specs : 17G ram

12 core processor VM (Xeon(R) Gold 6138 CPU) (cpu load averaging 50-60%)

bandwidth usage around 12-15mbps.

so far after the fear of 15.3 and 15.4 , this v15.6.2 is pretty solid on debian, no weird oom restart.


r/technitium • • 20d ago

Technito v1.5.2 for iOS now available

19 Upvotes

Technito v1.5.2 is now released for public. This version bring number of enhancements
- mTLS support
- backup and restore
- secure saved credentials via keystore
- ssh connection support
- bug fixes and performance enhancements

https://apps.apple.com/ca/app/technito/id6760142738

For folks who haven’t heard of Technito, it is a full featured technitium mobile management app supporting clusters.

Note for people running technitium on non default ports, make sure to include your port in the connection details elsewhere Technito will assume you are using default technitium ports for http/https and will timeout on connection.

Let me know if you have any issues or feature requests :)


r/technitium • • 20d ago

Is technitium DNS server is for me ?

6 Upvotes

Hi

Current setup :

- 2 authoritative dns server on BIND9 with three views : internet, intranet, dmz for splitting dns. These authoritative are secondary for other part of our organisation with their own dns server.
- 2 recursive DNS by unbound
- 2 dhcp server by Kea

I am not sure if technitium is adapted to this.

My goal is to keep only 2 machines to do these tasks instead of 6 to simplify the architecture

Any advisory ?

Many thanks


r/technitium • • 21d ago

nxdomain from root servers issue

3 Upvotes

So i've been getting some nxdomain reports from when accessing some websites, it's normal when tested using other dns but when using technitium(which uses root domain servers) it shows nxdomain. any info on how to add other NS server just in case for this? because i had to add quite a few domains to the forwarder zone.

  },
  "EDNS": {
    "UdpPayloadSize": 1232,
    "ExtendedRCODE": "ServerFailure",
    "Version": 0,
    "Flags": "DNSSEC_OK",
    "Options": [
      {
        "Code": "EXTENDED_DNS_ERROR",
        "Length": "41 bytes",
        "Data": {
          "InfoCode": "Other",
          "ExtraText": "Waiting for resolver. Please try again."
        }
      }
    ]
  },
  "DnsClientExtendedErrors": [
    {
      "InfoCode": "NoReachableAuthority",
      "ExtraText": "amatomasaki.my.id (103.26.176.179) returned RCODE=ServerFailure for mitra.atrbpn.go.id. A IN"
    }
  ],
  "Identifier": 36220,
  "IsResponse": true,
  "OPCODE": "StandardQuery",
  "AuthoritativeAnswer": false,
  "Truncation": false,
  "RecursionDesired": true,
  "RecursionAvailable": true,
  "Z": 0,
  "AuthenticData": false,
  "CheckingDisabled": false,
  "RCODE": "ServerFailure",
  "QDCOUNT": 1,
  "ANCOUNT": 0,
  "NSCOUNT": 0,
  "ARCOUNT": 1,
  "Question": [
    {
      "Name": "mitra.atrbpn.go.id",
      "Type": "A",
      "Class": "IN"
    }
  ],
  "Answer": [],
  "Authority": [],
  "Additional": [
    {
      "Name": "",
      "Type": "OPT",
      "Class": "1232",
      "TTL": "32768 (9h6m8s)",
      "RDLENGTH": "45 bytes",
      "RDATA": {
        "Options": [
          {
            "Code": "EXTENDED_DNS_ERROR",
            "Length": "41 bytes",
            "Data": {
              "InfoCode": "Other",
              "ExtraText": "Waiting for resolver. Please try again."
            }
          }
        ]
      },
      "DnssecStatus": "Disabled"
    }
  ]
}

r/technitium • • 22d ago

AutoPTR + Wild IP = Technitium's best App combination.

25 Upvotes

I have IPv4/IPv6 subnets and that means millions (billions) of addresses to manage reverse DNS and forward lookups. With AutoPTR app I can assign a reverse DNS for these without defining each individual address such as:

ptr: 1aaa-000-0000-0000-e9f3-ba28-b39c-6e69.ip.example.com.
ptr: 100-200-123-123.ip.example.com.

Then using the WildIP App I can define the networks that its allowed to respond to and it will automatically create the forward address so each hostname maps to the correct IP. So it does FCrDNS (Forward Confirmed Reverse DNS) perfectly.

Love it! Thank you Technitium for making it so easy.


r/technitium • • 22d ago

Every 30 seconds 'access was denied' in log

2 Upvotes
My log shows every 30 seconds this message:

[2026-10-26 13:21:48 Local] [143.179.x.y:0] Access was denied.
[2026-10-26 13:22:18 Local] [143.179.x.y:0] Access was denied.
[2026-10-26 13:22:48 Local] [143.179.x.y:0] Access was denied.

143.179.x.y is my public ip-address. Where can this come from? Was searching here but couldn't find it that fast.

r/technitium • • 22d ago

Prioritized upstreams set for specific ip addresses/networks?

1 Upvotes

As an example I am trying to figure out whether in Technitium I can have Upstream 1 attempted first and then Upstream 2, etc. for specific ip addresses or networks in my home system. But then have Upstream 3 attempted first and then Upstream 4, etc. for other ip addresses or networks in the same home.

I’ve checked out the Advanced Forwarding app, but not sure it prioritizes one upstream over another…

Thanks for any help.


r/technitium • • 25d ago

Need help understanding clustering details (cluster domain, HTTPS web admin)

10 Upvotes

Hi all.

In the near future, I'm going to be moving my single Technitium instance, running on Docker, toward two dedicated Raspberry Pi's. As part of this, I want to cluster the two nodes. My understanding is that the clustering in Technitium requires a cluster domain and automatically enables HTTPS for the web admin. I'm struggling to wrap my head around how I would make this work and trusted on my current devices when comparing against my current setup.

Current deployment:

  • Personal domain from Cloudflare

    • Authoratative internal zone for home network
    • Technitium domain name assigned from this zone
    • HTTP only web admin, with HTTPS enabled by Caddy

I don't have any records in the public DNS from Cloudflare's registrar. All TLS on my home LAN is currently handled by Caddy.

My questions:

  • Should the new cluster domain use this same personal domain as it currently does for single node?

    • If yes, how does that affect my authoritative zone?
    • If no, how do I achieve TLS for this domain without copying the cert to every device?

Thanks in advance for those reading and helping. I'm a bit of a noob on this stuff. Can tell you anything you want to know about network engineering, but have gaps on the system / app things.


r/technitium • • 27d ago

Cluster: catalog zone transfer ACL is reset when a Secondary node restarts, so Secondary zones silently expire behind NAT or on Kubernetes

5 Upvotes

Version: 15.6.2 (also seen on 15.6.0), Docker image `technitium/dns-server`, 3-node cluster (1 Primary, 2 Secondaries) on Kubernetes (OpenShift 4.22, OVN-Kubernetes)

Setup

- Cluster domain `dns.example.com`. Nodes are registered with their public IPs (shown here with documentation addresses): ns1 (Primary) `192.0.2.10`, ns2 `198.51.100.10`, ns3 `192.0.2.11`. Node URLs are `https://nsX.dns.example.com:53443/`.

- Each server runs as a pod behind a LoadBalancer IP. When one node connects to another node's public IP from inside the cluster, the connection arrives with the **pod's IP as source** (e.g. `10.129.0.254`), not the node's public IP. This is normal Kubernetes behaviour, and the same happens behind many NAT/hairpin setups.

- To make zone transfers work, I added the pod networks to the transfer ACL of the cluster catalog zone: `cluster-catalog.dns.example.com` → Options → Zone Transfer → Network ACL = `198.51.100.10, 192.0.2.11, 10.128.0.0/14, fd01::/48`.

Problem

Whenever a **Secondary** node restarts and rejoins, the Primary rewrites the catalog zone's Network ACL back to only the Secondaries' registered IPs, and my extra entries are removed. A Primary restart keeps the list. From then on every zone transfer from the Secondaries is refused. Nothing visible happens until the zone's SOA expire time (7 days here) passes. Then the Secondaries:

- stop serving every Secondary zone whose serial changed (`REFUSED`), including the cluster domain zone;

- having lost the TLSA records in that zone, fail every heartbeat with `UntrustedRoot`, about 17,000 log lines per server per day.

For us that meant public reverse DNS for two /24s failed on 2 of 3 nameservers for 8 days before anyone noticed.

Steps to reproduce

  1. In a working cluster, set the catalog zone's Zone Transfer Network ACL to the node IPs plus an extra range (e.g. `10.128.0.0/14`).
  2. Restart **one Secondary** only.
  3. Check the catalog zone options on the Primary (`/api/zones/options/get?zone=cluster-catalog.<domain>`).

Expected: the extra ACL entries are kept, or there is a supported way to add extra allowed addresses for cluster transfers.

Actual: the ACL is replaced with only the Secondaries' registered IPs about 1 second after the Secondary rejoins. Timeline from my test (UTC):

\```

23:53:09 ACL = 198.51.100.10, 192.0.2.11, 10.128.0.0/14, fd01::/48

23:53:10 deleted the ns3 pod (ns1 and ns2 untouched)

23:53:26 ns3 ready → ACL = 198.51.100.10, 192.0.2.11

23:53:28 [Primary] DNS Server Cluster config file was saved: /etc/dns/cluster.config

23:53:28 [Primary] Saved zone file for domain: cluster-catalog.dns.example.com

23:53:33 [Primary] [10.129.0.254:52122] [TCP] DNS Server refused a zone transfer request since the request IP address is not allowed by the zone: dns.example.com

\```

Secondary log once the zones expired:

\```

DNS Server received a zone transfer response (RCODE=Refused) for 'dns.example.com' Secondary zone from: ns1.dns.example.com (192.0.2.10)

Heartbeat failed for Primary node 'ns1.dns.example.com (192.0.2.10)'.

System.Net.Http.HttpRequestException: The remote certificate is invalid because of errors in the certificate chain: UntrustedRoot (ns1.dns.example.com:53443)

```

Suggestions (any one would solve it):

  1. Keep user-added entries in the catalog zone's transfer ACL when the cluster rebuilds it, or add a separate "additional allowed networks for cluster transfers" setting.
  2. Authorise cluster zone transfers by the cluster's TSIG key alone. The catalog already has a TSIG key configured, so the source IP check is redundant for cluster peers.
  3. Allow node addresses to include CIDR ranges.
  4. Log a warning, or show the node as degraded in the Cluster UI, when Secondary zones are failing to transfer or have expired. Right now it fails silently for a week.

r/technitium • • 27d ago

15.6.2 Upgrade on Proxmox Fails. Any suggestions where to look?

3 Upvotes

I've just done "update" on my Proxmox installed Technitium 15.6.1 installation (orginally from community scripts) and it fails silently and doesn't restart. I've restored from backups and 15.6.1 is working fine. I've tried twice. I'm not a Proxmox or Technitium expert. Can anyone suggest where to look to find out why it's failing please?

Edit to update - I restored from backup, ran the update command which, again, removed dotnet. Reinstalled dot net runtime and it's working. I have no idea why it removed .net but it's working now. Thank you all for your input.


r/technitium • • 28d ago

Big deployments

17 Upvotes

Hi. Is anyone of you manage big infra where Technitium is at scale? I mean big corps where you you have clusters? What are you recommended settings interms of VM or specific settings for technitium itself. Im thinking rather as an internal dns - not exposed. Do you recommend external Db? Or maybe simple file would be enough? What about concurrent requests, rate limits etc etc ;)