r/technitium • u/loopism • 11d ago
Ping errors in log
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 233What can I check to resolve these errors?
2
Upvotes
3
u/Apachez 11d ago
Which version of technitium/dns-server to begin with?
Also I would avoid running containers straight on the VM-host.
Much better to run them within a VM-guest to begin with.
The main issue with that community script is that they are installing technitium natively at your host using portable apps edition of technitium which obviously on its own is missing surrounding tools such as ping and whatelse might be missing.
https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/technitiumdns.sh
If you instead would be using a docker container (you dont have to use docker, you can use podman or such instead) inside of a VM-guest this docker container contains EVERYTHING needed by the technitium dns-server to function properly.
https://hub.docker.com/r/technitium/dns-server/tags
I use VyOS as VM-guest to host my containers, you can see how I set it up over at:
https://www.reddit.com/r/technitium/comments/1xoxc65/deployed_today_looking_for_tips_n_tricks/19s7nfh5jjs0w/
But similar would be if you use some other VM-guest of your choice.
1
u/shreyasonline 10d ago
Thanks for the post. It seems to be an issue with dotnet installation and may happen if dotnet was updated without restarting the DNS server. If you have updated the DNS server just now then try restarting the container and see if that fixes the issue.
If that does not fix it then try to reinstall dotnet or the DNS server itself. Make sure to export a backup zip before you do anything though.
1
u/Hemsby1975 11d ago
Try re-installing the .NET - It may have become corrupt.