Strange issue:

systemd-resolved reports the first-in-list dns server as the "current" dns server being used

open firefox, visit URL that could be resolved by first-in-list server

changes the current DNS server to the last-in-list server.

Any of ya'll experience this?

It *seems* that having four DNS servers in list causes some sort of buffer-overflow. I can't prove this except for having experienced this weird behaviour

Show thread

Have you watched the network traffic?
My idea is that all servers are contacted round robin and the first that answers becomes the current server.

@fredl99 If that's the case then I'll have to set pfSense to perform lookups for things it doesn't find.

This is probably what I should have done in the first place

It was only an idea. You should examine that before changing anything.
With Linux iptraf could be helpful for this.

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.