Local domain problem
I set the local domain in ‘settings?tab=settings’ to: 'homenuc.local' and the domain in advanced settings to ‘homenuc.local’. Then I configured adguard and added the dns to the router so that traffic goes through adguard and it works. Then I added to adguard: ‘dns_rewrites’:
- domain: homenuc.local
- 192.168.68.64
192.168.68.64 is the ip of my local server.
But still homenuc.local is not working why?
From another computer on the network I checked and I have something like this:
nslookup homenuc.local
Server: 192.168.68.64
Address: 192.168.68.64#53
Non-authoritative answer:
Name: homenuc.local
Address: 192.168.68.64
so it should work but it doesn't.
34 Replies
Hello, first of all the domain and local domain are two different things with different configurations. You should not use the same value in both of these. The moment you remove the .local from the domain value Runtipi should work. One small note is that I recommend against using .local because it's reserved for mdns. Instead use something like .lan which is a pseudo one.
thanks for fast answer but
Changed domain name in advanced settings to: homenuc.example
Local domain changed to: homenuc.lan
Changed configuration in adguard from local to lan.
Server rebooted and still not working
So if you to homenuc.lan what do you get?
in chrome i get this:
Check for an error in the homenuc.lan address.
DNS_PROBE_FINISHED_NXDOMAIN
But nsloomup shows it gets the IP?
yep from client pc:
nslookup homenuc.lan
Server: 192.168.68.64
Address: 192.168.68.64#53
Non-authoritative answer:
Name: homenuc.lan
Address: 192.168.68.64
Alright try to use an incognito window
It may be cache
log from server resolvectl status:
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign
DNS Servers: 127.0.0.1
Fallback DNS Servers: 1.1.1.1
DNS Domain: lan
Link 2 (eno1)
Current Scopes: none
Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no
Link 3 (wlp1s0)
Current Scopes: DNS
Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
DNS Servers: 192.168.68.64 1.1.1.1
Default Route: yes
Link 4 (br-10dd7ca9c40c)
Current Scopes: none
Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no
Link 5 (br-15457005dbfe)
Current Scopes: none
Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no
Link 6 (br-b76b2bf871a6)
Current Scopes: none
Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no
Link 7 (br-d46900d0de7b)
Current Scopes: none
Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no
Link 8 (docker0)
Current Scopes: none
I checked it in incognico mode, in opera and firefox. it doesn't work either
What if you use curl
So this means your DNS isn't working, can you try to remove the 1.1.1.1
ok i made this chenges in /etc/systemd/resolved.conf:
DNS=127.0.0.1
#FallbackDNS=1.1.1.1
Domains=lan
#DNSSEC=no
#DNSOverTLS=no
MulticastDNS=no
LLMNR=no
#Cache=yes
#CacheFromLocalhost=no
DNSStubListener=no
systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; preset: enabled)
Active: active (running) since Fri 2025-07-25 09:24:17 UTC; 1min 4s ago
Invocation: 064cbdc0bdaf432a97719071132211f3
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS
https://systemd.io/WRITING_RESOLVER_CLIENTS
Main PID: 22394 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 12369)
Memory: 3M (peak: 3.2M)
CPU: 125ms
CGroup: /system.slice/systemd-resolved.service
└─22394 /usr/lib/systemd/systemd-resolved
lip 25 09:24:16 homenuck systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
lip 25 09:24:17 homenuck systemd-resolved[22394]: Positive Trust Anchors:
lip 25 09:24:17 homenuck systemd-resolved[22394]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
lip 25 09:24:17 homenuck systemd-resolved[22394]: . IN DS 38696 8 2 683d2d0acb8c9b712a1948b27f741219298d0a450d612c483af444a4c0fb2b16
lip 25 09:24:17 homenuck systemd-resolved[22394]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in->
lip 25 09:24:17 homenuck systemd-resolved[22394]: Using system hostname 'homenuck'.
lip 25 09:24:17 homenuck systemd[1]: Started systemd-resolved.service - Network Name Resolution.
i use ubuntu 25.04
Wait, the server running runtipi should not use the DNS server
(if it's hosted on runtipi)
You should set the DNS in the client machine
on the router I have dns set to 192.168.68.64
And are you sure your client is using that?
Link 3 (wlp1s0)
Current Scopes: DNS
Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
DNS Servers: 192.168.68.64 1.1.1.1
Default Route: yes
it should only use your local dns
not 1.1.1.1
hmm... when I set the router to only 192.168.68.64 I dont have internet connection
something broken with dns....
w8 i reinstall ubuntu and set runtipi from 0
then i change local domain to homenuc.lan
install adguard and add to dns_rewrites
to install adguard i should disable?
sudo systemctl disable systemd-resolved
wait wait wait
you simply have to install runtipi
edit the
/etc/resolv.conf file and for nameservers use something like 1.1.1.1
(may be different if you are using network manager but it will let you know by saying that hey this file is managed by network manager)
and then just install the adguard app in runtipi
and set your dns rewrites
then use the ip of that machine as your dns server and dont use any secondary like 1.1.1.11. Installed clean Runtipi
2. sudo systemctl stop systemd-resolved
3. sudo systemctl disable systemd-resolved
4. add 'homenuc.lan' to dns_rewrites adguard
5.
/etc/resolv.conf not exist if disable systemd-resolved
6. router have first dns 192.168.68.64 and second dns 1.1.1.1
7. homenuc.lan not working xDCan the machine running runtipi access homenuc.lan
from server its working:
ping homenuc.lan
PING homenuc.lan (192.168.68.64) 56(84) bytes of data.
64 bytes from 192.168.68.64: icmp_seq=1 ttl=64 time=0.041 ms
64 bytes from 192.168.68.64: icmp_seq=2 ttl=64 time=0.051 ms
64 bytes from 192.168.68.64: icmp_seq=3 ttl=64 time=0.049 ms
64 bytes from 192.168.68.64: icmp_seq=4 ttl=64 time=0.046 ms
64 bytes from 192.168.68.64: icmp_seq=5 ttl=64 time=0.047 ms
64 bytes from 192.168.68.64: icmp_seq=6 ttl=64 time=0.046 ms
64 bytes from 192.168.68.64: icmp_seq=7 ttl=64 time=0.044 ms
This means that your server is using your DNS but your client isn't
in client wifi settings i have this dns server
Can you remove the 1.1.1.1?
it's not a good solution because if the server stops working I won't have the internet
Well that's how DNS works : )
If you have 1.1.1.1
adguard won't be able to block anything
which i believe is the primary reason for wanting a dns server?
Is there any option to disable https and use http?
hmm... and is there any other option to use domains instead of ip and ports?
you can use a ddns service
or buy a domain
nope, it's for security reasons
i recommend you buy a domain from cloudflare/porkbun for ~10 euro/year
then not only can you point it to runtipi but you can also get valid ssl certificates
you can also use these ddns service like duckdns but they are quite unreliable (ddns doesn't have to point to public ips)
in any case seems weird to me that your mac ignores the dns server because it's clearly working
I guess I will have to do so, I will just buy a domain and it will be quiet. then I will not need adguard?
very strange that mac can't see but i don't have the strength to do it anymore....
i will buy a domain and see what happens. thanks a lot for your help 🙂
Nope, you just point your domain or a subdomain to your server's ip
Trust me, a domain is worth it
Just pick something short
Will it work even if it's ip from the local network?
Yes
I only use local IPs in my domain