Re: electrons/the Internet doesn't like question authority niggahs?, or is it that I like to eat raw garlic, ...
On 3/4/24 08:37, Albretch Mueller wrote:
<rant>
Yes, networking problems are infuriating.
Something that shouldn't be happening at all is that after I use
traceroute once, it doesn't work again and my Internet access speed
describes like a sinus curve which amplitude remains for the most part
under 16KiB per second and for more than one second as 0B per second.
_LINK="https://christuniversity.in/uploads/course/E&Comp_21-25_Lateral
Entry(1)_20210618043317.pdf"
I have AT&T Internet service in Tracy, California.
My daily driver is:
2024-03-04 10:47:12 dpchrist@laalaa ~
$ cat /etc/debian_version ; uname -a
11.9
Linux laalaa 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31)
x86_64 GNU/Linux
When I click the above link in my mail client (Thunderbird), my browser
(Firefox) attempts to open the URL. But, the URL is mangled by mail
client line wrap and/or indentation (?), and the connection times out:
https://christuniversity.in/uploads/course/E&Comp_21-25_Lateral
An error occurred during a connection to christuniversity.in.
The site could be temporarily unavailable or too busy. Try again in
a few moments.
If you are unable to load any pages, check your computer’s network
connection.
If your computer or network is protected by a firewall or proxy,
make sure that Firefox is permitted to access the web.
The following URL's also time out (see DNS comments, below):
http://christuniversity.in/
http://103.105.225.131/
http://111.93.136.229/
https://christuniversity.in/
https://103.105.225.131/
https://111.93.136.229/
1) is the file actually there?:
wget -q --spider "${_LINK}"; _WGETQ=$?
I refrain from spidering web sites -- being blackholed is not good.
$ ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 204 Mar 3 18:59 /etc/resolv.conf
2024-03-04 10:50:49 dpchrist@laalaa ~
$ ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 83 Mar 4 09:50 /etc/resolv.conf
$ cat /etc/resolv.conf
# Generated by NetworkManager
# nameserver 192.168.1.254
# nameserver 192.168.68.1
# https://serverfault.com/questions/76421/wget-cant-resolve-host
# RED 2013-03-31
nameserver 8.8.8.8
nameserver 8.8.4.4
2024-03-04 10:51:32 dpchrist@laalaa ~
$ cat /etc/resolv.conf
# Generated by NetworkManager
search tracy.holgerdanske.com
nameserver 192.168.5.1
I believe Debian rewrites /etc/resolv.conf on every boot.
Hard coding Google Public DNS servers should work, but letting your
gateway do it for your LAN is easier to manage, is faster, and conserves
WAN bandwidth. I would revert your changes.
And, Google is watching you.
STFW for DNS privacy:
https://avoidthehack.com/best-dns-privacy
I think I will configure my gateway to use Quad9:
https://www.quad9.net/service/locations/
The next level up would be DNS over TLS (DoT), DNS over HTTPS (DoH),
DNSCrypt, etc.:
https://en.wikipedia.org/wiki/DNS_over_TLS
$ ls -l /etc/nsswitch.conf
-rw-r--r-- 1 root root 613 Mar 3 12:57 /etc/nsswitch.conf
2024-03-04 10:52:04 dpchrist@laalaa ~
$ ls -l /etc/nsswitch.conf
-rw-r--r-- 1 root root 542 Jan 9 2022 /etc/nsswitch.conf
$ cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: files
group: files
shadow: files
gshadow: files
#hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
hosts: files dns mdns4_minimal [NOTFOUND=return] dns myhostname
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
2024-03-04 10:56:37 dpchrist@laalaa ~
$ cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: files systemd
group: files systemd
shadow: files
gshadow: files
hosts: files mdns4_minimal [NOTFOUND=return] dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
It appears my /etc/nsswitch.conf has not been touched since
installation. I would revert your changes.
; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> +time christuniversity.in
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49715
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;christuniversity.in. IN A
;; ANSWER SECTION:
christuniversity.in. 60 IN A 103.105.225.131
christuniversity.in. 60 IN A 111.93.136.229
;; Query time: 327 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Mon Mar 04 05:42:58 CST 2024
;; MSG SIZE rcvd: 80
Please post complete console sessions with a useful PS1 to provide
context, the exact command issued, and the exact output displayed (with
redactions indicated):
2024-03-04 10:57:52 dpchrist@laalaa ~
$ dig christuniversity.in
; <<>> DiG 9.16.48-Debian <<>> christuniversity.in
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39687
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;christuniversity.in. IN A
;; ANSWER SECTION:
christuniversity.in. 60 IN A 103.105.225.131
christuniversity.in. 60 IN A 111.93.136.229
;; Query time: 248 msec
;; SERVER: 192.168.5.1#53(192.168.5.1)
;; WHEN: Mon Mar 04 11:10:24 PST 2024
;; MSG SIZE rcvd: 80
Note that there are two A records for christuniversity.in.
PING christuniversity.in (103.105.225.131) 56(84) bytes of data.
--- christuniversity.in ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3080ms
Your ping went to the first A record IPv4 address. I get the same result:
2024-03-04 11:41:50 dpchrist@laalaa ~
$ ping -c 3 103.105.225.131
PING 103.105.225.131 (103.105.225.131) 56(84) bytes of data.
--- 103.105.225.131 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2045ms
If I use the FQDN, I can ping the second A record IPv4 address:
2024-03-04 11:10:24 dpchrist@laalaa ~
$ ping -c 3 christuniversity.in
PING christuniversity.in (111.93.136.229) 56(84) bytes of data.
64 bytes from 111.93.136.229 (111.93.136.229): icmp_seq=1 ttl=49 time=272 ms
64 bytes from 111.93.136.229 (111.93.136.229): icmp_seq=2 ttl=49 time=272 ms
64 bytes from 111.93.136.229 (111.93.136.229): icmp_seq=3 ttl=49 time=272 ms
--- christuniversity.in ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 271.856/272.182/272.371/0.231 ms
I suggest trying to ping 111.93.136.229.
traceroute to christuniversity.in (111.93.136.229), 30 hops max, 60 byte packets
1 _gateway (192.168.68.1) 16.964 ms 15.714 ms 17.508 ms
2 * 192.168.1.254 (192.168.1.254) 18.381 ms *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 ix-be-39.ecore1.ct8-chicago.as6453.net (66.198.27.4) 64.819 ms
64.547 ms 64.685 ms
10 if-ae-44-2.tcore1.ct8-chicago.as6453.net (63.243.129.56) 80.053
ms 81.180 ms 85.409 ms
11 if-ae-26-2.tcore3.nto-newyork.as6453.net (216.6.81.28) 86.478 ms
* 81.806 ms
12 if-ae-34-14.tcore4.njy-newark.as6453.net (66.198.111.26) 81.795
ms if-ae-34-15.tcore4.njy-newark.as6453.net (66.198.111.58) 84.297 ms
82.801 ms
13 if-ae-1-3.tcore3.njy-newark.as6453.net (216.6.57.5) 97.965 ms
88.660 ms 89.184 ms
14 66.198.70.10 (66.198.70.10) 306.240 ms * 301.191 ms
15 * * *
16 * * *
17 * * *
18 111.93.136.229 (111.93.136.229) 307.868 ms 313.512 ms 306.604 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Using the first A record IPv4 address:
2024-03-04 11:42:34 dpchrist@laalaa ~
$ traceroute 103.105.225.131
traceroute to 103.105.225.131 (103.105.225.131), 30 hops max, 60 byte
packets
1 ubnttracyholgerdanskecom (192.168.5.1) 0.370 ms 0.520 ms 0.687 ms
2 attlocal.net (192.168.1.254) 2.763 ms 3.142 ms 3.641 ms
3 76-201-76-1.lightspeed.frokca.sbcglobal.net (76.201.76.1) 21.651
ms 22.421 ms 23.062 ms
4 71.147.234.9 (71.147.234.9) 26.820 ms 30.000 ms 27.644 ms
5 * * *
6 * * *
7 32.130.91.81 (32.130.91.81) 35.002 ms 35.741 ms 36.905 ms
8 192.205.32.182 (192.205.32.182) 41.690 ms 30.204 ms 27.039 ms
9 cablewireless-ic-382397.ip.twelve99-cust.net (62.115.46.249)
27.853 ms 29.772 ms 30.216 ms
10 ae15-xcr1.tyo.cw.net (195.2.20.125) 136.239 ms 137.968 ms 137.056 ms
11 195.2.10.193 (195.2.10.193) 201.657 ms 202.155 ms 205.131 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Using the FQDN:
2024-03-04 11:14:07 dpchrist@laalaa ~
$ traceroute christuniversity.in
traceroute to christuniversity.in (111.93.136.229), 30 hops max, 60 byte
packets
1 ubnttracyholgerdanskecom (192.168.5.1) 0.375 ms 0.522 ms 0.689 ms
2 attlocal.net (192.168.1.254) 2.925 ms 3.659 ms 4.147 ms
3 76-201-76-1.lightspeed.frokca.sbcglobal.net (76.201.76.1) 22.249
ms 23.117 ms 25.102 ms
4 71.147.234.9 (71.147.234.9) 28.279 ms 29.195 ms 30.719 ms
5 * * *
6 * * *
7 32.130.91.81 (32.130.91.81) 38.078 ms 39.616 ms *
8 64.86.160.14 (64.86.160.14) 46.002 ms 27.525 ms 26.610 ms
9 64.86.160.3 (64.86.160.3) 38.830 ms * *
10 * if-ae-20-2.tcore2.sv1-santaclara.as6453.net (66.198.101.132)
44.654 ms *
11 * * *
12 * * *
13 66.110.59.114 (66.110.59.114) 273.586 ms 274.232 ms 277.765 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
I do not see any meaningful clues in any of the traceroute(8) outputs.
I suspect there could be two root causes -- conflicting DNS A records
and the web server is down and/or broken by the DNS issue.
Doing a whois lookup, christuniversity.in does not provide contact
information; only email@publicdomainregistry.com:
https://www.whois.com/whois/christuniversity.in
David
Reply to: