You are not logged in.
i reinstalled arch. my problems are fixed.
hopefully this works.
This is not a problem that you can fix with a re-installation
does not block 1.1.1.1 as far as I am concerned (it used to work before I broke dns), and the other is campus internet (eduroam) which also does not block 1.1.1.1 either
This is not about the IP, I guess "ping -c 1.1.1.1" still works, but the port; 53 being for DNS.
This helps to force you to use a specific DNS server to control your access to information - except that https://wiki.archlinux.org/title/DNS_over_HTTPS_servers exists.
if it were a problem i couldnt have solved with a reinstallation, why does it work now?
i use arch (since Nov 1, 2024) btw
Offline
dig @1.1.1.1 archlinux.org
Offline
dig @1.1.1.1 archlinux.org
wow it really doesnt work, i have no idea what is wrong with this country. 8.8.8.8 works, but 1.1.1.1 doesnt:
$ dig @1.1.1.1 archlinux.org
;; communication error to 1.1.1.1#53: timed out
x3
; <<>> DiG 9.20.3 <<>> @1.1.1.1 archlinux.org
; (1 server found)
;; global options: +cmd
;; no servers could be reached
i am guessing at campus grounds 1.1.1.1 was indeed working but at dorm grounds it is banned. i have no idea. really. im sorry for the headache i may or may not have caused guys.
edit: and it works again??? on dorm grounds??? guys when i tell you i have no idea why it does or does not work i mean it. i literally havent changed anything in the setup and now this works:
$ dig @1.1.1.1 archlinux.org
; <<>> DiG 9.20.3 <<>> @1.1.1.1 archlinux.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50454
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: cc95dfb9f41ea39253eac589672e561736a88cf1c0e32e78 (good)
;; QUESTION SECTION:
;archlinux.org. IN A
;; ANSWER SECTION:
archlinux.org. 1617 IN A 95.217.163.246
;; Query time: 33 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Fri Nov 08 21.09.03 +03 2024
;; MSG SIZE rcvd: 86
Last edited by voxell (2024-11-08 18:31:07)
i use arch (since Nov 1, 2024) btw
Offline
The most likely explanation is that it's not the IP but the network connection itself is flaky, not necessarily inside the LAN, though.
You could try to keep "ping 1.1.1.1" and "ping _gateway" running in the background and see whether one or both of them at some point start to timeout.
Offline