Should I mark this as solved???
If it is, then yes.
]]> ~ stat /etc/resolv.conf ✔
File: /etc/resolv.conf
Size: 53 Blocks: 8 IO Block: 4096 regular file
Device: 259,1 Inode: 18482213 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2021-10-06 19:09:56.898000228 +0530
Modify: 2021-10-06 19:09:51.231333651 +0530
Change: 2021-10-06 19:09:51.231333651 +0530
Birth: 2021-10-06 19:09:51.231333651 +0530
The issue is no longer there. I've been watching udemy videos for the past 2 days with no problems. And amazon website is also rendered properly.
Sorry for the late reply. I didn't notice that this thread had continued till the 2nd page.
Should I mark this as solved???
How do you configure the network itfp?
install network manager and enable the NetworkManager service
systemd-resolved will be used automatically if /etc/resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf, /run/systemd/resolve/resolv.conf or /usr/lib/systemd/resolv.conf.
stat /etc/resolv.conf
W/ systemd-resolved now being enabled, does the issue continue eg. after a reboot?
]]>I didn't configure anything of that sort.(itfp)
How did you install archlinux? What tutorial did you follow?
]]> ~ sudo systemctl status systemd-resolved ✔ took 6s
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
Active: active (running) since Mon 2021-10-04 12:54:26 IST; 13min ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 3772 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 9407)
Memory: 4.7M
CPU: 272ms
CGroup: /system.slice/systemd-resolved.service
└─3772 /usr/lib/systemd/systemd-resolved
Oct 04 12:54:26 Arch systemd[1]: Starting Network Name Resolution...
Oct 04 12:54:26 Arch systemd-resolved[3772]: Positive Trust Anchors:
Oct 04 12:54:26 Arch systemd-resolved[3772]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Oct 04 12:54:26 Arch systemd-resolved[3772]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in>
Oct 04 12:54:26 Arch systemd-resolved[3772]: Using system hostname 'Arch'.
Oct 04 12:54:26 Arch systemd[1]: Started Network Name Resolution.
Oct 04 12:54:26 Arch systemd-resolved[3772]: wlp0s20f3: Bus client set default route setting: yes
Oct 04 12:54:26 Arch systemd-resolved[3772]: wlp0s20f3: Bus client set DNS server list to: 192.168.0.1
Oct 04 12:54:33 Arch systemd-resolved[3772]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.0.1.
Oct 04 12:54:33 Arch systemd-resolved[3772]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.0.1.
Maybe it did start after me restarting. Yeah I just enabled the service.So that means it wasn't starting of it's own.
I didn't configure anything of that sort.(itfp)
I did that following a post online where the person had the same problem as me. But it didn't have any effect. I'll put it back.
]]> ~ cat /etc/nsswitch.conf 1 ✘
# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.
passwd: files systemd
group: files [SUCCESS=merge] systemd
shadow: files
publickey: files
hosts: files mymachines myhostname resolve dns
networks: files
protocols: files
services: files
ethers: files
rpc: files
netgroup: files
~ ps aux | grep resolved ✔
~ 0|1 ✘
~ resolvectl query images-na.ssl-images-amazon.com INT ✘
images-na.ssl-images-amazon.com: resolve call failed: Unit dbus-org.freedesktop.resolve1.service not found.
The second command didn't return anything.
I don't knowing if restarting the service worked or what but now both websites are loading properly. Do you know what might be the reason??
The curl and ping commands from above are now working.
]]>cat /etc/nsswitch.conf
ps aux | grep resolved
resolvectl query images-na.ssl-images-amazon.com
In doubt, restart systemd-resolved.service
]]> ~ dig images-na.ssl-images-amazon.com ✔
; <<>> DiG 9.16.21 <<>> images-na.ssl-images-amazon.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59357
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 13, ADDITIONAL: 11
;; QUESTION SECTION:
;images-na.ssl-images-amazon.com. IN A
;; ANSWER SECTION:
images-na.ssl-images-amazon.com. 8795 IN CNAME m.media-amazon.com.
m.media-amazon.com. 31 IN CNAME c.media-amazon.com.
c.media-amazon.com. 20 IN A 54.230.236.57
;; AUTHORITY SECTION:
com. 95613 IN NS g.gtld-servers.net.
com. 95613 IN NS f.gtld-servers.net.
com. 95613 IN NS c.gtld-servers.net.
com. 95613 IN NS h.gtld-servers.net.
com. 95613 IN NS e.gtld-servers.net.
com. 95613 IN NS j.gtld-servers.net.
com. 95613 IN NS i.gtld-servers.net.
com. 95613 IN NS k.gtld-servers.net.
com. 95613 IN NS b.gtld-servers.net.
com. 95613 IN NS l.gtld-servers.net.
com. 95613 IN NS m.gtld-servers.net.
com. 95613 IN NS a.gtld-servers.net.
com. 95613 IN NS d.gtld-servers.net.
;; ADDITIONAL SECTION:
a.gtld-servers.net. 4579 IN A 192.5.6.30
b.gtld-servers.net. 112443 IN A 192.33.14.30
c.gtld-servers.net. 46786 IN A 192.26.92.30
d.gtld-servers.net. 46894 IN A 192.31.80.30
e.gtld-servers.net. 112053 IN A 192.12.94.30
f.gtld-servers.net. 47150 IN A 192.35.51.30
g.gtld-servers.net. 44965 IN A 192.42.93.30
h.gtld-servers.net. 45004 IN A 192.54.112.30
i.gtld-servers.net. 47458 IN A 192.43.172.30
j.gtld-servers.net. 45818 IN A 192.48.79.30
k.gtld-servers.net. 47510 IN A 192.52.178.30
;; Query time: 3 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Mon Oct 04 12:37:07 IST 2021
;; MSG SIZE rcvd: 510
~ dig @8.8.8.8 images-na.ssl-images-amazon.com ✔
; <<>> DiG 9.16.21 <<>> @8.8.8.8 images-na.ssl-images-amazon.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55213
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;images-na.ssl-images-amazon.com. IN A
;; ANSWER SECTION:
images-na.ssl-images-amazon.com. 21205 IN CNAME m.media-amazon.com.
m.media-amazon.com. 25 IN CNAME c.media-amazon.com.
c.media-amazon.com. 25 IN A 54.230.236.57
;; Query time: 56 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Oct 04 12:38:08 IST 2021
;; MSG SIZE rcvd: 121
~ nslookup images-na.ssl-images-amazon.com INT ✘
Server: 192.168.0.1
Address: 192.168.0.1#53
Non-authoritative answer:
images-na.ssl-images-amazon.com canonical name = m.media-amazon.com.
m.media-amazon.com canonical name = c.media-amazon.com.
Name: c.media-amazon.com
Address: 54.230.236.57
Name: c.media-amazon.com
Address: 2600:9000:2056:7e00:1d:d7f6:39cf:a761
Name: c.media-amazon.com
Address: 2600:9000:2056:ae00:1d:d7f6:39cf:a761
Name: c.media-amazon.com
Address: 2600:9000:2056:f800:1d:d7f6:39cf:a761
Name: c.media-amazon.com
Address: 2600:9000:2056:9000:1d:d7f6:39cf:a761
Name: c.media-amazon.com
Address: 2600:9000:2056:7000:1d:d7f6:39cf:a761
Name: c.media-amazon.com
Address: 2600:9000:2056:8a00:1d:d7f6:39cf:a761
Name: c.media-amazon.com
Address: 2600:9000:2056:b800:1d:d7f6:39cf:a761
Name: c.media-amazon.com
Address: 2600:9000:2056:6600:1d:d7f6:39cf:a761
~ ping -c1 images-na.ssl-images-amazon.com ✔
ping: images-na.ssl-images-amazon.com: Temporary failure in name resolution
dig images-na.ssl-images-amazon.com
dig @8.8.8.8 images-na.ssl-images-amazon.com
nslookup images-na.ssl-images-amazon.com
ping -c1 images-na.ssl-images-amazon.com
]]> ~ curl -v 'https://images-na.ssl-images-amazon.com/images/I/01JqOTGW4hL.css?xcp' > /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Could not resolve host: images-na.ssl-images-amazon.com
* Closing connection 0
curl: (6) Could not resolve host: images-na.ssl-images-amazon.com
]]>curl -v 'https://images-na.ssl-images-amazon.com/images/I/01JqOTGW4hL.css?xcp' > /dev/null
]]>