Hi there,
this is my first install of nixos (gnome edition) and instantly it delivers something special → a problem around dns-lookups … but maybe its something else.
(may be related to DNS Lookup Problems)
Since my first start i can visit websites only sometimes. Lets say ddg.gg (duckduckgo) or youtube
At first the browser says “not available”
5 Minutes later it works and i can watch videos etc
another 5 mins later youtube stops to work, but ddg.gg still works - or the other way around. URLs work or cease to work randomly over time … Sometimes a website loads, sometimes not. This is browser behaviour since my first install 2 days ago.
First i made sure my router works properly and my other machines can visit the same websites on the same network at the same time without any outages. Nixos is connected via cable (Ethernet). No VPN here.
i placed
networking.nameservers = [ "1.1.1.1" "9.9.9.9" ];
into /etc/nixos/configuration
my /etc/resolve.conf now is:
# Generated by resolvconf
search Speedport_W_723V_1_41_000
nameserver 192.168.2.1
nameserver fe80::1%enp2s0
nameserver 1.1.1.1
nameserver 9.9.9.9
options edns0
No change in behaviour.
Then i started ping’ing and dig’ging. After nixos start, i open terminal and ping ddg.gg successfully. Then i open firefox and it can’t connect to ddg.gg. Then i go back to console and ping ddg.gg fails. 10 minutes later it works again …
fascinating thing is that dig resolves the correct ip address while ping fails :
[water@nixos:~]$ ping blog.fefe.de
ping: blog.fefe.de: Name or service not known
[water@nixos:~]$ dig blog.fefe.de
;; Warning: Message parser reports malformed message packet.
; <<>> DiG 9.18.24 <<>> blog.fefe.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60199
;; flags: qr aa rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;blog.fefe.de. IN A
;; ANSWER SECTION:
. 0 CLASS1232 OPT 10 8 tFncTcYkF8Q=
;; ADDITIONAL SECTION:
blog.fefe.de. 78467 IN A 31.15.64.162
;; Query time: 0 msec
;; SERVER: 192.168.2.1#53(192.168.2.1) (UDP)
;; WHEN: Tue Mar 12 16:31:33 CET 2024
;; MSG SIZE rcvd: 69
[water@nixos:~]$ ping blog.fefe.de
ping: blog.fefe.de: Name or service not known
[water@nixos:~]$ ping 31.15.64.162
PING 31.15.64.162 (31.15.64.162) 56(84) bytes of data.
64 bytes from 31.15.64.162: icmp_seq=1 ttl=53 time=20.7 ms
64 bytes from 31.15.64.162: icmp_seq=2 ttl=53 time=20.6 ms
64 bytes from 31.15.64.162: icmp_seq=3 ttl=53 time=20.8 ms
64 bytes from 31.15.64.162: icmp_seq=4 ttl=53 time=21.2 ms
64 bytes from 31.15.64.162: icmp_seq=5 ttl=53 time=20.4 ms
64 bytes from 31.15.64.162: icmp_seq=6 ttl=53 time=20.5 ms
64 bytes from 31.15.64.162: icmp_seq=7 ttl=53 time=20.6 ms
64 bytes from 31.15.64.162: icmp_seq=8 ttl=53 time=20.7 ms
64 bytes from 31.15.64.162: icmp_seq=9 ttl=53 time=20.7 ms
64 bytes from 31.15.64.162: icmp_seq=10 ttl=53 time=20.9 ms
64 bytes from 31.15.64.162: icmp_seq=11 ttl=53 time=20.6 ms
64 bytes from 31.15.64.162: icmp_seq=12 ttl=53 time=20.6 ms
64 bytes from 31.15.64.162: icmp_seq=13 ttl=53 time=20.5 ms
^C
--- 31.15.64.162 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12022ms
rtt min/avg/max/mdev = 20.376/20.676/21.150/0.190 ms
Seems like something is footgunning around here, but what exactly ??
I’m not really into networking, so i have no clue where to look at now.
any help appreciated
and got me to the point switching back to an arch distro now. This eats too much time.
for that