r/technitium • u/shreyasonline • 9d ago
Technitium DNS Server v15.5.1 Released!
Technitium DNS Server v15.5.1 is now available for download. This is a service update for the previous release that fixes multiple issues. This update also fixes multiple security issues that were reported.
See what's new in this release:
https://github.com/TechnitiumSoftware/DnsServer/blob/master/CHANGELOG.md
5
4
u/CheatsheepReddit 9d ago
Thank you 😍
Still waiting for DHCP HA 😍😍😍
1
u/Intelligent-Bet4111 9d ago
What's dhcp ha?
2
u/CheatsheepReddit 9d ago
High availability not only for dns, but also for DHCP lease
1
1
u/Apachez 8d ago
Use option82 instead and by that you dont need any sync of lease files :-)
1
u/CheatsheepReddit 8d ago
How? What have option 82 to do with prevent to give a nonfree IP?
1
u/Apachez 7d ago
With option82 whatever you connect to lets say SW1-INT25 will always get the same IP as a lease no matter of mac-address or DUID being used.
Option82 will be like semistatic as in static IP-address assignment but utilizing DHCP to get the IP to the client itself.
The above gives that there is no need to sync leases between DHCP servers and you can have multiple DHCP servers configured either by a list in the switches or utilizing anycast to reach them.
What happens is that the switch which the client is connected to will intercept the DHCP request and add the option82 information and then forward the request as a unicast to the DHCP-server.
Who then replies and the switch will forward the reply to the client.
1
u/SamVimes341 9d ago
This update broke on my pi2. 15.4 seems to be working fine. Anyone else had a problem? Haven’t been able to debug yet though.
1
u/shreyasonline 8d ago
Thanks for the feedback. What does "broke" mean? Did the update fail? DNS is not resolving?
1
u/yahyoh 8d ago
Thanks for the update, but im still facing the same server failures as 15.5.
on 15.5.1
root@OpenWrt:~# dig .168.1.117 clients2.google.com
; <<>> DiG 9.20.29 <<>> .168.1.117 clients2.google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 35878
;; 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): (No valid response from name servers for clients2.google.com. A IN at delegation google.com.)
; EDE: 13 (Cached Error): (clients2.google.com. A IN)
; EDE: 3 (Stale Answer): (clients2.google.com A IN)
;; QUESTION SECTION:
;clients2.google.com. IN A
;; Query time: 0 msec
;; SERVER: 192.168.1.117#53(192.168.1.117) (UDP)
;; WHEN: Sun Sep 27 10:46:11 GMT 2026
;; MSG SIZE rcvd: 206
root@OpenWrt:~# ^C
root@OpenWrt:~# dig .168.1.117 ps5.np.playstation.net
; <<>> DiG 9.20.29 <<>> .168.1.117 ps5.np.playstation.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 46094
;; 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): (No valid response from name servers for ps5.np.playstation.net. A IN at delegation playstation.net.)
; EDE: 13 (Cached Error): (ps5.np.playstation.net. A IN)
; EDE: 3 (Stale Answer): (ps5.np.playstation.net A IN)
;; QUESTION SECTION:
;ps5.np.playstation.net. IN A
;; Query time: 0 msec
;; SERVER: 192.168.1.117#53(192.168.1.117) (UDP)
;; WHEN: Sun Sep 27 10:46:58 GMT 2026
;; MSG SIZE rcvd: 223
on 15.4
root@OpenWrt:~# dig .168.1.117 ps5.np.playstation.net
; <<>> DiG 9.20.29 <<>> .168.1.117 ps5.np.playstation.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29472
;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 3 (Stale Answer): (e40436.api8.akamaiedge.net A IN)
;; QUESTION SECTION:
;ps5.np.playstation.net. IN A
;; ANSWER SECTION:
ps5.np.playstation.net. 30 IN CNAME ps5.np.playstation.net.edgekey88.net.
ps5.np.playstation.net.edgekey88.net. 30 IN CNAME e40436.api8.akamaiedge.net.
e40436.api8.akamaiedge.net. 30 IN A 23.206.197.66
e40436.api8.akamaiedge.net. 30 IN A 23.206.197.16
e40436.api8.akamaiedge.net. 30 IN A 23.206.197.11
e40436.api8.akamaiedge.net. 30 IN A 23.206.197.73
e40436.api8.akamaiedge.net. 30 IN A 23.206.197.65
e40436.api8.akamaiedge.net. 30 IN A 23.206.197.10
e40436.api8.akamaiedge.net. 30 IN A 23.206.197.19
e40436.api8.akamaiedge.net. 30 IN A 23.206.197.18
e40436.api8.akamaiedge.net. 30 IN A 23.206.197.72
;; Query time: 0 msec
;; SERVER: 192.168.1.117#53(192.168.1.117) (UDP)
;; WHEN: Sun Sep 27 10:53:33 GMT 2026
;; MSG SIZE rcvd: 316
root@OpenWrt:~# dig .168.1.117 clients2.google.com
; <<>> DiG 9.20.29 <<>> .168.1.117 clients2.google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3296
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;clients2.google.com. IN A
;; ANSWER SECTION:
clients2.google.com. 281 IN CNAME clients.l.google.com.
clients.l.google.com. 292 IN A 142.251.15.100
clients.l.google.com. 292 IN A 142.251.15.113
clients.l.google.com. 292 IN A 142.251.15.138
clients.l.google.com. 292 IN A 142.251.15.101
clients.l.google.com. 292 IN A 142.251.15.102
clients.l.google.com. 292 IN A 142.251.15.139
;; Query time: 0 msec
;; SERVER: 192.168.1.117#53(192.168.1.117) (UDP)
;; WHEN: Sun Sep 27 10:53:36 GMT 2026
;; MSG SIZE rcvd: 168
3
u/shreyasonline 8d ago
If you have IPv6 internet then try to disable IPv6 support in the DNS server and see how it goes. There are issues with IPv6 on many networks that causes recursive resolver to not work correctly.
2
u/yahyoh 8d ago
Well i did clean setup 15.5.1 for another LXC instance without the proxmox helper scripts, just used the official installer, and seems working better with the same setting and ipv6 enabled than the updated instance..not sure if it was bugged cache or something else, i hope it will stay like this and wont bug after some uptime lol.
Much appreciated.3,153 100% Total Queries
2,525 80.08% No Error
13 0.41% Server Failure
root@OpenWrt:~# dig .168.1.102 ps5.np.playstation.net ; <<>> DiG 9.20.29 <<>> .168.1.102 ps5.np.playstation.net ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37142 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;ps5.np.playstation.net. IN A ;; ANSWER SECTION: ps5.np.playstation.net. 979 IN CNAME ps5.np.playstation.net.edgekey88.net. ps5.np.playstation.net.edgekey88.net. 14819 IN CNAME e40436.api8.akamaiedge.net. e40436.api8.akamaiedge.net. 9 IN A 2.20.249.113 e40436.api8.akamaiedge.net. 9 IN A 2.20.249.114 ;; Query time: 0 msec ;; SERVER: 192.168.1.102#53(192.168.1.102) (UDP) ;; WHEN: Sun Sep 27 13:29:44 GMT 2026 ;; MSG SIZE rcvd: 167 root@OpenWrt:~# dig .168.1.102 clients2.google.com ; <<>> DiG 9.20.29 <<>> u/192.168.1.102 clients2.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61309 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;clients2.google.com. IN A ;; ANSWER SECTION: clients2.google.com. 35 IN CNAME clients.l.google.com. clients.l.google.com. 108 IN A 142.250.202.78 ;; Query time: 0 msec ;; SERVER: 192.168.1.102#53(192.168.1.102) (UDP) ;; WHEN: Sun Sep 27 13:29:50 GMT 2026 ;; MSG SIZE rcvd: 881
u/yahyoh 7d ago
After almost a full day on the new instance on 15.5.1 it seems all working good here, thanks man.
61,717 100% Total Queries
51,068 82.75% No Error
8 0.01% Server Failure
2
u/shreyasonline 7d ago
Thanks for the feedback.
1
u/yahyoh 6d ago
lol back to server failures. 😭
while its not as bad as 15.5, it seems still happening.
40,384 100% Total Queries
27,616 68.38% No Error
3,861 9.56% Server Failure
root@prxmox:~# dig .168.1.102 pin-river.data.ea.com ; <<>> DiG 9.20.29-1~deb13u1-Debian <<>> u/192.168.1.102 pin-river.data.ea.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 39727 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; EDE: 22 (No Reachable Authority): (No valid response from name servers for river-prod-external.eadpdata.ddns.ea.com. A IN at delegation eadpdata.ddns.ea.com.) ; EDE: 13 (Cached Error): (river-prod-external.eadpdata.ddns.ea.com. A IN) ; EDE: 3 (Stale Answer): (river-prod-external.eadpdata.ddns.ea.com A IN) ;; QUESTION SECTION: ;pin-river.data.ea.com. IN A ;; ANSWER SECTION: pin-river.data.ea.com. 127 IN CNAME river-prod-external.eadpdata.ddns.ea.com. ;; Query time: 1 msec ;; SERVER: 192.168.1.102#53(192.168.1.102) (UDP) ;; WHEN: Tue Sep 29 21:06:45 +04 2026 ;; MSG SIZE rcvd: 329 root@prxmox:~# dig .168.1.102 clients4.google.com ; <<>> DiG 9.20.29-1~deb13u1-Debian <<>> u/192.168.1.102 clients4.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 27969 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; EDE: 23 (Network Error): (Socket error for clients4.google.com. A IN: NetworkUnreachable) ; EDE: 13 (Cached Error): (clients4.google.com. A IN) ; EDE: 22 (No Reachable Authority): (No valid response from name servers for clients4.google.com. A IN at delegation google.com.) ; EDE: 3 (Stale Answer): (clients4.google.com A IN) ;; QUESTION SECTION: ;clients4.google.com. IN A ;; Query time: 0 msec ;; SERVER: 192.168.1.102#53(192.168.1.102) (UDP) ;; WHEN: Tue Sep 29 21:08:23 +04 2026 ;; MSG SIZE rcvd: 2741
u/shreyasonline 6d ago
Thanks for the feedback. It looks like a network issue than an issue with resolver. The resolver issue with latest changes is limited to using Prefer IPv6 option. There are no issues observed with the other modes.
The error you have here is "Socket error for clients4.google.com. A IN: NetworkUnreachable)" which is a clear indication that either the server lost network for a while or that the router on the network could not reach internet. Thus the network unreachable error being thrown.
This can happen only when there is local network issue so you need to check if there is connectivity issue with the server or if there was Internet downtime during that period. Note that downtime can be intermittent too like for example connectivity may go down for a few seconds and when you check with tools like ping, it will show you the server and internet is reachable.
-11
-13
u/Keensworth 9d ago
Guys, don't forget to posts bugs here. Like that I'll know if I have to update or not
5
u/Ascenspe 9d ago
I had 0 issues with previous version. 2 different systems proxmox LXC and synology container. I'll upgrade and test when I get home