The network configuration has already told you in previous post. All network is in virtualbox adapter.
How to check whether the internet connection are DNSSEC compliant?
I use dig to check the dnslookup as below figure:
A test on my system ( no VM! ) gives
dig +dnssec @127.0.1 pypi.tuna.tsinghua.edu.cn
;; communications error to 127.0.0.1#53: timed out
; <<>> DiG 9.20.1 <<>> +dnssec @127.0.1 pypi.tuna.tsinghua.edu.cn
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33882
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 1232
;; QUESTION SECTION:
;pypi.tuna.tsinghua.edu.cn. IN A
;; ANSWER SECTION:
pypi.tuna.tsinghua.edu.cn. 296 IN CNAME mirrors.tuna.tsinghua.edu.cn.
mirrors.tuna.tsinghua.edu.cn. 56 IN CNAME bfdmirrors.s.tuna.tsinghua.edu.cn.
bfdmirrors.s.tuna.tsinghua.edu.cn. 297 IN A 101.6.15.130
;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.1) (UDP)
;; WHEN: Tue Nov 26 15:14:30 CET 2024
;; MSG SIZE rcvd: 119
Is there any way to disable DNSSEC? Let me verify whether it is the DNSSEC problem that causes the occasional failure of nslookup.
1 Like
I also want to let everyone know, that 8.8.4.4 is the primary and 8.8.8.8 is the redundant in Google’s DNS cluster. So your system should be querying 8.8.4.4 first if using Google Public DNS.
1 Like
That’s the first time I ever heard this. I have seen so many configs and never seen 8.8.4.4 as primary
I would say it doesn’t matter if the right power supply is running and the left one is not, the right one is call redundancy or vice versa.
Normally, however, both power supply units are running to be redundancy.
1 Like
That is what I noticed. maybe because 8.8.8.8 is easy to memorise?