Hello everyone...
I'm currently experimenting with Technitium DNS [as a replacement for my current PiHole machines] and although I have it working well, I have an issue where it is disregarding requested configuration settings for network addresses. I'd be grateful for any suggestions anyone can offer in regards to [preferably] resolving or [if not] triaging the issue.
Thanks in advance.
If you'd like to read a discussion of the problem and some triage I've done with the Technitium folk, you can find that here:-
https://github.com/TechnitiumSoftware/D ... 3952395323
Problem Statement
When running the latest edition of Technitium DNS and when having the DNS configured to use a specific IP Address on a multi-homed Raspberry Pi, Technitium appears to disregard the preference setting and resorts to using the "primary" or "first" IP address as defined by the nmtui command line utility.
The most relevant piece of information I've found in experimenting with the developers is that when they attempt to recreate my issue on a Pi, they see the problem, but when they try it on a different machine running ubuntu, the software works as expected.
The problem is as follows:-
Start with a pair of Raspberry Pi machines, which we'll call "Primary" and "Secondary". Give the machines the following IP Addresses:-
Primary
172.16.103.21 [host main IP address]
172.16.103.211 [DNS service on this host]
Secondary
172.16.103.24 [host main IP address]
172.16.103.241 [DNS service on this host]
Technitium DNS fully supports the use of AXFR/IXFR data transfers between Primary and Secondary DNS servers, using TCP socket 53 [or 853] to do so. However, even though I can set up my two Pi machines to serve DNS requests exclusively on the two VIP addresses ['211 and '241'], when I set up Technitium to synchronise records between Primary and Secondary, the Secondary Pi sends all the traffic out over the '24 IP address and not the '241 address.
If I perform clean installations of Raspberry Pi OS [these are lab machines] and then give them just the '211 and '241 IP addresses, replication works as expected. If I then add the '21 and '24 IP addresses on to the hosts, it also works. However, if I then use "ip addr", all my assigned IP addresses appear out-of-order in the response. But if I go in and manually adjust the configuration file ( in /etc/NetworkManager/system-connections/ and re-test, traffic simply reverts to the '24 IP address.
Even though Technitium has a parameter for "outbound traffic" which ubuntu supports, the Pi does not.
This isn't end-of-the-world territory, of course, but the reason I use VIPs for services on my Pi infrastructure is that when I'm looking at network traffic, I can easily tell what I'm looking at simply from the addresses - because each network service gets to operate out of a dedicated IP address...
Can anyone suggest why there might be operational differences between ubuntu and Raspberry Pi OS - and if this can be addressed?
Thanks in advance.
I'm currently experimenting with Technitium DNS [as a replacement for my current PiHole machines] and although I have it working well, I have an issue where it is disregarding requested configuration settings for network addresses. I'd be grateful for any suggestions anyone can offer in regards to [preferably] resolving or [if not] triaging the issue.
Thanks in advance.
If you'd like to read a discussion of the problem and some triage I've done with the Technitium folk, you can find that here:-
https://github.com/TechnitiumSoftware/D ... 3952395323
Problem Statement
When running the latest edition of Technitium DNS and when having the DNS configured to use a specific IP Address on a multi-homed Raspberry Pi, Technitium appears to disregard the preference setting and resorts to using the "primary" or "first" IP address as defined by the nmtui command line utility.
The most relevant piece of information I've found in experimenting with the developers is that when they attempt to recreate my issue on a Pi, they see the problem, but when they try it on a different machine running ubuntu, the software works as expected.
The problem is as follows:-
Start with a pair of Raspberry Pi machines, which we'll call "Primary" and "Secondary". Give the machines the following IP Addresses:-
Primary
172.16.103.21 [host main IP address]
172.16.103.211 [DNS service on this host]
Secondary
172.16.103.24 [host main IP address]
172.16.103.241 [DNS service on this host]
Technitium DNS fully supports the use of AXFR/IXFR data transfers between Primary and Secondary DNS servers, using TCP socket 53 [or 853] to do so. However, even though I can set up my two Pi machines to serve DNS requests exclusively on the two VIP addresses ['211 and '241'], when I set up Technitium to synchronise records between Primary and Secondary, the Secondary Pi sends all the traffic out over the '24 IP address and not the '241 address.
If I perform clean installations of Raspberry Pi OS [these are lab machines] and then give them just the '211 and '241 IP addresses, replication works as expected. If I then add the '21 and '24 IP addresses on to the hosts, it also works. However, if I then use "ip addr", all my assigned IP addresses appear out-of-order in the response. But if I go in and manually adjust the configuration file ( in /etc/NetworkManager/system-connections/ and re-test, traffic simply reverts to the '24 IP address.
Even though Technitium has a parameter for "outbound traffic" which ubuntu supports, the Pi does not.
This isn't end-of-the-world territory, of course, but the reason I use VIPs for services on my Pi infrastructure is that when I'm looking at network traffic, I can easily tell what I'm looking at simply from the addresses - because each network service gets to operate out of a dedicated IP address...
Can anyone suggest why there might be operational differences between ubuntu and Raspberry Pi OS - and if this can be addressed?
Thanks in advance.
Statistics: Posted by sproggit — Tue Feb 24, 2026 7:25 pm — Replies 0 — Views 27