You are not logged in.

#1 2025-09-10 20:59:16

jessy65
Member
Registered: 2025-09-07
Posts: 1

Arch Linux systemd-resolved issues when hosting a small test website

Hi,

I’ve been experimenting with running a small website on Arch Linux using Apache + PHP. Everything works locally, but I’ve been facing DNS resolution issues when trying to access the site from another machine on the same network.

I configured systemd-resolved with custom DNS servers.

Sometimes ping works fine, but Apache doesn’t resolve hostnames.

Restarting systemd-resolved temporarily fixes it, then it breaks again.

As a demo, I’ve been testing with a small project (example: https://fashionismic.com/
) just to see how multiple pages behave.

Questions:

Is there a known issue with systemd-resolved on Arch when combined with Apache/MariaDB?

Would it be better to disable systemd-resolved and use resolv.conf directly?

Is dnsmasq a better lightweight option for local web development on Arch?

Any guidance or config tips from Arch users who’ve dealt with similar DNS problems would be appreciated.


A Web Developer And Designer

Offline

#2 2025-09-10 22:41:11

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,314

Re: Arch Linux systemd-resolved issues when hosting a small test website

Everything works locally, but I’ve been facing DNS resolution issues when trying to access the site from another machine on the same network.

Can you elaborate on the "DNS resolution issues"? Why would and DNS resolution failure on the server depend on the client??
What domains does apache have to resolve?
What are the actual symptoms? ("I do X and expect Y but then Z happens")
Are other processes on the server affected?
What custom dns servers did you configure?

Restarting systemd-resolved temporarily fixes it

very much sounds like a race condition, please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Offline

#3 2025-09-11 14:30:48

twelveeighty
Member
Registered: 2011-09-04
Posts: 1,446

Re: Arch Linux systemd-resolved issues when hosting a small test website

In addition to seth's points in post #2: if a client cannot resolve your server's hostname, then the problem most likely is on the client, not the server. You'll have to give us some logs and/or exact error messages from the *client* to start with.

I would also strongly recommend taking Apache/MariaDB completely out of the picture and first get your DNS working. Use lower level tools such as `dig`, `ping`, etc. on the clients until you're satisfied that DNS is all good across the network.

Offline

Board footer

Powered by FluxBB