You are not logged in.

#1 2016-09-03 13:57:06

lls123
Member
Registered: 2016-09-03
Posts: 2

Some domains cannot be resolved (systemd-resolved) - CNAME?

Hi everybody,

I'm totally new to Archlinux and ran into strange problems.regarding the DNS resolution.

My system is using systemd-resolved and some domains cannot be resolved (e.g. www.youtube.com or archlinux.org)
This issue seems only affects domains which are using a CNAME record.

Is there any "magic" setting to enable this?

Thank you!

Luke

Offline

#2 2016-09-05 13:25:51

cyayon
Member
Registered: 2016-09-05
Posts: 35

Re: Some domains cannot be resolved (systemd-resolved) - CNAME?

Hi,

Same problem here.

Any solution ?

Offline

#3 2016-09-05 13:36:30

lls123
Member
Registered: 2016-09-03
Posts: 2

Re: Some domains cannot be resolved (systemd-resolved) - CNAME?

As workround I've changed in file /etc/nsswitch.conf the line

hosts: file dns myhostname
to:
hosts: file resolve myhostname

Offline

#4 2016-09-05 13:42:31

cyayon
Member
Registered: 2016-09-05
Posts: 35

Re: Some domains cannot be resolved (systemd-resolved) - CNAME?

my nsswitch is already like this, but no luck...

Offline

#5 2016-09-21 09:18:12

eigengrau
Member
Registered: 2013-09-19
Posts: 43

Re: Some domains cannot be resolved (systemd-resolved) - CNAME?

This appears to be a bug in the systemd-resolved stub resolver. Using «resolve» in nsswitch.conf should work around the issue for applications using the glibc API. When applications query DNS directly via resolv.conf, this won’t work until the bug has been resolved.

Edit: I guess one thing you could do is replace the /etc/resolve.conf symlink with a link targeting /var/run/systemd/resolve/resolv.conf. This will make such applications circumvent the stub resolver, while the glibc API will still use systemd-resolved.

Last edited by eigengrau (2016-09-21 09:22:38)

Offline

Board footer

Powered by FluxBB