You are not logged in.
I use `doh-client` with adding `nameserver 127.0.0.1` into `/etc/resolv.conf`. But the `docker-compose build` cannot resolve the address of `apt` dependencies :/
It turns into normal after I removing the `127.0.0.1` from resolv.conf.
Is there a way to let these two work together?
Last edited by unamed^^ (2024-01-01 03:40:24)
Σ(-᷅_-᷄๑)
Offline
Have you tried following https://wiki.archlinux.org/title/DNS-over-HTTPS ?
Welcome to archlinux forums.
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
Offline
Sorry for the delay
Have you tried following https://wiki.archlinux.org/title/DNS-over-HTTPS ?
Yes I'm currently using this implementation as my local DoH client.
I'm mainly using 1.1.1.1:
# DNS listen port
listen = [
"127.0.0.1:53",
"127.0.0.1:5380",
"[::1]:53",
"[::1]:5380",
## To listen on both 0.0.0.0:53 and [::]:53, use the following line
# ":53",
]
...
[[upstream.upstream_ietf]]
url = "https://cloudflare-dns.com/dns-query"
weight = 50
...Welcome to archlinux forums.
Tysm!
Σ(-᷅_-᷄๑)
Offline
Please post /etc/resolv.conf contents and output of
$ find /etc/systemd -type l -exec realpath '{}' \+Does nslookup www.google.com work with 127.0.0.1 in resolv.conf ?
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
Offline
Please post /etc/resolv.conf contents and output of
$ find /etc/systemd -type l -exec realpath '{}' \+
> find /etc/systemd -type l -exec realpath '{}' \+
/usr/lib/systemd/system/sddm.service
/usr/lib/systemd/system/NetworkManager-wait-online.service
/usr/lib/systemd/system/systemd-resolved.service
/usr/lib/systemd/system/bluetooth.service
/usr/lib/systemd/system/doh-client.service
/usr/lib/systemd/system/tlp.service
/usr/lib/systemd/system/NetworkManager.service
/usr/lib/systemd/system/remote-fs.target
/usr/lib/systemd/system/docker.service
/usr/lib/systemd/system/NetworkManager-dispatcher.service
/usr/lib/systemd/system/systemd-timesyncd.service
/usr/lib/systemd/system/systemd-resolved.service
/usr/lib/systemd/system/systemd-timesyncd.service
/usr/lib/systemd/system/getty@.service
/usr/lib/systemd/system/bluetooth.service
/usr/lib/systemd/user/p11-kit-server.socket
/usr/lib/systemd/user/pipewire-pulse.socket
/usr/lib/systemd/user/pipewire.socket
/usr/lib/systemd/user/gcr-ssh-agent.socket
/usr/lib/systemd/user/xdg-user-dirs-update.service
/usr/lib/systemd/user/wireplumber.service
/usr/lib/systemd/user/wireplumber.serviceAnd
> cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 127.0.0.1Does nslookup www.google.com work with 127.0.0.1 in resolv.conf ?
Yes,
dig google.com@127.0.0.1
; <<>> DiG 9.18.20 <<>> google.com@127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12819
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;google.com\@127.0.0.1. IN A
;; AUTHORITY SECTION:
. 86400 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2023121800 1800 900 604800 86400
;; Query time: 59 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Mon Dec 18 01:35:32 PST 2023
;; MSG SIZE rcvd: 124Σ(-᷅_-᷄๑)
Offline
/usr/lib/systemd/system/systemd-resolved.servicesystemd-resolved is not very good at cooperating with other dns resolution methods.
In order to get this to work you'll have to configure systemd-resolved , NetworkManager and doh-client to work together.
Taking systemd-resolved out of the equation may be the best way to simplify your DNS resolution setup .
Some links for background info
https://wiki.archlinux.org/title/Openresolv
https://wiki.archlinux.org/title/System … NS_servers
https://wiki.archlinux.org/title/Networ … management
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
Offline
Sorry for the delay - I'm on my break.
/usr/lib/systemd/system/systemd-resolved.serviceTaking systemd-resolved out of the equation may be the best way to simplify your DNS resolution setup .
Tysm! This works for me so far (by disabled and stopped that service in systemctl)
Happy new year!
Σ(-᷅_-᷄๑)
Offline
Glad to have helped.
Please prepend [Solved] to the thread title (edit first post).
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
Offline