Arch Linux

wuhwuh

Member

Registered: 2025-04-19

Posts: 5

Local DNS uses old IP address

Hi,

I'm using systemd-resolved and have the following issue:

Trying to connect to a second machine on my local LAN via DNS name fails. I have a local router which also serves as a DNS server, and apparently it returns multiple entries for a DNS record:

> drill MYSERVER.fritz.box
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 172
;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 3 
;; QUESTION SECTION:
;; MYSERVER.fritz.box.       IN      A

;; ANSWER SECTION:
MYSERVER.fritz.box.  9       IN      A       192.168.178.27
MYSERVER.fritz.box.  9       IN      A       192.168.178.51

;; AUTHORITY SECTION:
MYSERVER.fritz.box.  9       IN      NS      fritz.box.

;; ADDITIONAL SECTION:
fritz.box.      9       IN      A       192.168.178.1
fritz.box.      9       IN      AAAA    fd3c:39cc:938:0:3ea6:2fff:fe57:56c7
fritz.box.      9       IN      AAAA    2a02:8071:5a70:720:3ea6:2fff:fe57:56c7

;; Query time: 2 msec
;; SERVER: 127.0.0.53
;; WHEN: Mon Apr 21 13:11:08 2025
;; MSG SIZE  rcvd: 157

The .27 is the correct address, but commands like xfreerdp3 end up using the old one, .51.

What I don't understand: It's working fine under both Windows and MacOS, otherwise I would assume the DNS on my local router is doing something weird. Am I missing some resolved configuration? And I had the same issue under Endeavour OS (I just switched to Arch), which uses NetworkManager.

I know I could set up static entries, but I would like to understand why this is an issue in the first place.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,335

Re: Local DNS uses old IP address

;; SERVER: 127.0.0.53

That looks like systemd-resolved is giving those answers.

Let's try asking your router directly , what is the output of

drill MYSERVER.fritz.box @192.168.178.1

?

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

wuhwuh

Member

Registered: 2025-04-19

Posts: 5

Re: Local DNS uses old IP address

> drill MYSERVER.fritz.box @192.168.178.1
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 64084
;; flags: qr aa rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 3 
;; QUESTION SECTION:
;; MYSERVER.fritz.box.       IN      A

;; ANSWER SECTION:
MYSERVER.fritz.box.  9       IN      A       192.168.178.27
MYSERVER.fritz.box.  9       IN      A       192.168.178.51

;; AUTHORITY SECTION:
MYSERVER.fritz.box.  9       IN      NS      fritz.box.

;; ADDITIONAL SECTION:
fritz.box.      9       IN      A       192.168.178.1
fritz.box.      9       IN      AAAA    fd3c:39cc:938:0:3ea6:2fff:fe57:56c7
fritz.box.      9       IN      AAAA    2a02:8071:5a70:720:3ea6:2fff:fe57:56c7

;; Query time: 1 msec
;; SERVER: 192.168.178.1
;; WHEN: Mon Apr 21 13:39:27 2025
;; MSG SIZE  rcvd: 157

EDIT: I also ran nslookup MYSERVER on a Windows machine (actually on MYSERVER itself) and it also returned both IP addresses. Is it maybe an application issue? As in, how applications handle multiple addresses being returned for a DNS query? I only tried ping and xfreerdp3, not sure what else I could test.

Last edited by wuhwuh (2025-04-21 11:46:39)

-thc

Member

Registered: 2017-03-15

Posts: 1,005

Re: Local DNS uses old IP address

If I'm not mistaken this is an issue outside Arch and your local machines.

Log in to your Router (Fritz!Box) and look into the active network client list (Heimnetz > Netzwerk). There should be two entries for your server - possibly both "active" at the same time. Shut down your server for some time and wait until the entries are "inactive". Delete the entries. Start your server. Only one new entry should be created.

Last edited by -thc (2025-04-21 12:19:03)

wuhwuh

Member

Registered: 2025-04-19

Posts: 5

Re: Local DNS uses old IP address

Thanks, and I (kind of) agree: It's not an Arch issue. It *might* be a linux issue (as in, linux is just designed differently in some places when compared to Windows or even macOS), but also nothing to actually fix. Again, *MIGHT*, I don't know enough to make that call, but it is working fine under the two other OSes I use.

I already did what you proposed and deleted the other entry on my router. It wasn't even marked as "active". However, now it's working. I will need to find a more permanent solution, but that's not a topic for this forum.

Thanks again!