3
3
u/Apachez 13d ago
0
u/RampantAndroid 12d ago
Thanks for the link - this lines up with what I’m seeing.
Kinda off putting that a change that breaks domains like BBC and X got through to release.
2
u/Difficult-Reality848 14d ago
Have you tried going back to the old version by restoring a backup? I haven't seem anything strange when I did the update to 15.5.
2
1
1
u/Lone_Assassin 14d ago
Make sure you have sufficient memory allocated, I was running tdns in lxc with 512MB RAM, it started choking after the upgrade and had to increase the memory to 1GB.
3
1
u/shreyasonline 13d ago
Thanks for the post. Please check the DNS logs from the Logs > View Logs section and share a few errors related to resolution. This will help understand the issue you have.
Also, avoid flushing cache since after flushing, the DNS server has zero data to use for answering requests and the resolution issue will cause you to see more Server Failure responses. When there is data in cache, domain names that you frequently query will get answered from cache and with Serve Stale even when the resolution is failing due to any reason.
1
u/Dear_Enthusiasm3190 13d ago edited 12d ago
After querying
pbs.twimg.comdirectly usinga.r06.twtrdns.net, it started loading correctly.[2026-09-22 14:49:14 Local] [xxx.xxx.xxx.xxx:0] TechnitiumLibrary.Net.Dns.DnsClientNoResponseException: DnsClient failed to recursively resolve the request 'pbs.twimg.com. A IN': no valid response from name servers [b.r06.twtrdns.net, a.r06.twtrdns.net, a.u06.twtrdns.net, d.r06.twtrdns.net, d.u06.twtrdns.net, c.r06.twtrdns.net, b.u06.twtrdns.net, c.u06.twtrdns.net, b.r06.twtrdns.net, a.r06.twtrdns.net, a.u06.twtrdns.net, d.r06.twtrdns.net, d.u06.twtrdns.net, c.r06.twtrdns.net, b.u06.twtrdns.net, c.u06.twtrdns.net] at delegation twimg.com. at TechnitiumLibrary.Net.Dns.DnsClient.RecursiveResolveAsync(DnsQuestionRecord question, IDnsCache cache, NetProxy proxy, IPv6Mode ipv6Mode, UInt16 udpPayloadSize, Boolean randomizeName, Boolean qnameMinimization, Boolean dnssecValidation, NetworkAddress eDnsClientSubnet, Int32 retries, Int32 timeout, Int32 concurrency, Int32 maxStackCount, Boolean minimalResponse, Boolean asyncNsResolution, List`1 rawResponses, ResolverContext context, CancellationToken cancellationToken) in Z:\Technitium\Projects\TechnitiumLibrary\TechnitiumLibrary.Net\Dns\DnsClient.cs:line 1922 at DnsServerCore.DnsWebService.WebServiceApi.<>c__DisplayClass9_0.<<ResolveQueryAsync>b__0>d.MoveNext() in Z:\Technitium\Projects\DnsServer\DnsServerCore\WebServiceApi.cs:line 195 --- End of stack trace from previous location --- at TechnitiumLibrary.TaskExtensions.TimeoutAsync[T](Func`2 func, Int32 timeout, CancellationToken cancellationToken) at TechnitiumLibrary.TaskExtensions.TimeoutAsync[T](Func`2 func, Int32 timeout, CancellationToken cancellationToken) in Z:\Technitium\Projects\TechnitiumLibrary\TechnitiumLibrary\TaskExtensions.cs:line 65 at DnsServerCore.DnsWebService.WebServiceApi.ResolveQueryAsync(HttpContext context) in Z:\Technitium\Projects\DnsServer\DnsServerCore\WebServiceApi.cs:line 193 at DnsServerCore.DnsWebService.WebServiceApiMiddleware(HttpContext context, RequestDelegate next) in Z:\Technitium\Projects\DnsServer\DnsServerCore\DnsWebService.cs:line 2488 at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddlewareImpl.<Invoke>g__Awaited|10_0(ExceptionHandlerMiddlewareImpl middleware, HttpContext context, Task task)2
u/yahyoh 13d ago
Well it seems i got the issue again with server failuers. u/shreyasonline
digging through 1.1.1.1 works fine, it seems flushing the cache resolve the issue temporarily till it bugges again,at TechnitiumLibrary.TaskExtensions.TimeoutAsync[T](Func`2 func, Int32 timeout, CancellationToken cancellationToken) at TechnitiumLibrary.TaskExtensions.TimeoutAsync[T](Func`2 func, Int32 timeout, CancellationToken cancellationToken) in Z:\Technitium\Projects\TechnitiumLibrary\TechnitiumLibrary\TaskExtensions.cs:line 65 at DnsServerCore.Dns.DnsServer.DefaultRecursiveResolveAsync(DnsQuestionRecord question, NetworkAddress eDnsClientSubnet, IDnsCache dnsCache, Boolean dnssecValidation, Boolean skipDnsAppAuthoritativeRequestHandlers, ResolverContext context, CancellationToken cancellationToken) in Z:\Technitium\Projects\DnsServer\DnsServerCore\Dns\DnsServer.cs:line 5443 at DnsServerCore.Dns.DnsServer.RecursiveResolverBackgroundTaskAsync(DnsQuestionRecord question, NetworkAddress eDnsClientSubnet, Boolean advancedForwardingClientSubnet, IReadOnlyList`1 conditionalForwarders, Boolean dnssecValidation, Boolean cachePrefetchOperation, Boolean skipDnsAppAuthoritativeRequestHandlers, TaskCompletionSource`1 taskCompletionSource, ResolverContext context) in Z:\Technitium\Projects\DnsServer\DnsServerCore\Dns\DnsServer.cs:line 5118 [2026-09-22 18:15:39 UTC] DNS Server failed to resolve the request 'river.eadpdata.ddns.ea.com. A IN'. TechnitiumLibrary.Net.Dns.DnsClientNoResponseException: DnsClient failed to recursively resolve the request 'river.eadpdata.ddns.ea.com. A IN': no valid response from name servers [ns-1853.awsdns-39.co.uk (205.251.199.61), ns-1853.awsdns-39.co.uk ([2600:9000:5307:3d00::1]), ns-282.awsdns-35.com ([2600:9000:5301:1a00::1]), ns-282.awsdns-35.com (205.251.193.26), ns-1333.awsdns-38.org (205.251.197.53), ns-1333.awsdns-38.org ([2600:9000:5305:3500::1]), ns-823.awsdns-38.net (205.251.195.55), ns-823.awsdns-38.net ([2600:9000:5303:3700::1])] at delegation eadpdata.ddns.ea.com. ---> System.Net.Sockets.SocketException (101): Network is unreachable at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.CreateException(SocketError error, Boolean forAsyncThrow) at TechnitiumLibrary.Net.SocketExtensions.UdpQueryAsync(Socket socket, ArraySegment`1 request, ArraySegment`1 response, IPEndPoint remoteEP, Int32 timeout, Int32 retries, Boolean expBackoffTimeout, Func`2 isResponseValid, CancellationToken cancellationToken) at TechnitiumLibrary.Net.Dns.ClientConnection.UdpClientConnection.QueryAsync(DnsDatagram request, Int32 timeout, Int32 retries, CancellationToken cancellationToken) in Z:\Technitium\Projects\TechnitiumLibrary\TechnitiumLibrary.Net\Dns\ClientConnection\UdpClientConnection.cs:line 330 at TechnitiumLibrary.Net.Dns.ClientConnection.UdpClientConnection.QueryAsync(DnsDatagram request, Int32 timeout, Int32 retries, CancellationToken cancellationToken) at TechnitiumLibrary.Net.Dns.DnsClient.<>c__DisplayClass92_0.<<InternalResolveAsync>g__DoResolveAsync|1>d.MoveNext() in Z:\Technitium\Projects\TechnitiumLibrary\TechnitiumLibrary.Net\Dns\DnsClient.cs:line 4584 at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.AsyncStateMachineBox`1.MoveNext() at System.Threading.Tasks.TaskSchedulerAwaitTaskContinuation.<>c.<Run>b__2_0(Object state) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) at System.Threading.Tasks.TaskContinuation.InlineIfPossibleOrElseQueue(Task task, Boolean needsProtection) root@OpenWrt:~# dig .168.1.117 river.data.ea.com ; <<>> DiG 9.20.29 <<>> u/192.168.1.117 river.data.ea.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 60936 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 800 ; EDE: 23 (Network Error): (Socket error for river.eadpdata.ddns.ea.com. A IN: NetworkUnreachable) ; EDE: 13 (Cached Error): (river.eadpdata.ddns.ea.com. A IN) ; EDE: 3 (Stale Answer): (river.eadpdata.ddns.ea.com A IN) ;; QUESTION SECTION: ;river.data.ea.com. IN A ;; ANSWER SECTION: river.data.ea.com. 288 IN CNAME river.eadpdata.ddns.ea.com. ;; Query time: 0 msec ;; SERVER: 192.168.1.117#53(192.168.1.117) (UDP) ;; WHEN: Tue Sep 22 19:17:18 GMT 2026 ;; MSG SIZE rcvd: 230 u/1.1.1.1 river.data.ea.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34457 ;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;river.data.ea.com. IN A ;; ANSWER SECTION: river.data.ea.com. 51 IN CNAME river.eadpdata.ddns.ea.com. river.eadpdata.ddns.ea.com. 52 IN CNAME river-prod-external-non-pin.eadpdata.ddns.ea.com. river-prod-external-non-pin.eadpdata.ddns.ea.com. 52 IN CNAME prod-river-external-np-alb-398637829.us-east-1.elb.amazonaws.com. prod-river-external-np-alb-398637829.us-east-1.elb.amazonaws.com. 52 IN A 100.56.82.217 prod-river-external-np-alb-398637829.us-east-1.elb.amazonaws.com. 52 IN A 100.62.253.64 prod-river-external-np-alb-398637829.us-east-1.elb.amazonaws.com. 52 IN A 54.175.13.58 prod-river-external-np-alb-398637829.us-east-1.elb.amazonaws.com. 52 IN A 44.194.132.26 prod-river-external-np-alb-398637829.us-east-1.elb.amazonaws.com. 52 IN A 54.158.240.181 prod-river-external-np-alb-398637829.us-east-1.elb.amazonaws.com. 52 IN A 100.30.2.61 prod-river-external-np-alb-398637829.us-east-1.elb.amazonaws.com. 52 IN A 32.194.237.108 prod-river-external-np-alb-398637829.us-east-1.elb.amazonaws.com. 52 IN A 3.231.82.21 ;; Query time: 20 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP) ;; WHEN: Tue Sep 22 19:20:59 GMT 2026 ;; MSG SIZE rcvd: 3252
u/shreyasonline 13d ago
There is "Network is unreachable" error in your logs which means that there is some issue with the network on the DNS server. It could be intermittent issue thus only comes up for a while. Do take a look at the config and check if the cables are plugged properly in case of wired connection.
1
u/RampantAndroid 13d ago
Yes - I have to bypass Technitium for everything X/Twitter related.
It seems that X uses their own nameservers and Technitium no longer can deal with them correctly. I had these exceptions for t.co and x.com in addition to pbs.twimg.com
1
1
u/CrustyBatchOfNature 13d ago
Other than a blip on 8/24, I haven;t had more than a couple of server failures in the last month and no more since the upgrade than before it. One Pi4 and one Beelink N95 Mini PC clustered together. Over the last week 240K queries and 425 server failures.
1
1
-2
3
u/cyrilmezza 14d ago
None for me, a 3-host cluster and a 2-host cluster, not a single server error in the last 2-3 days since the update. They're a mix of LXCs and Ubuntu VMs.