Adjust "Upstream DNS Providers"

[weyCC81]

Versions

N/A

Platform

N/A

Expected behavior

N/A

Actual behavior / bug

N/A

Steps to reproduce

N/A

Debug Token

N/A

Screenshots

Additional context

Remove DNS.WATCH?

Who is running this?

• https://dns.watch/

Adjust Google for IPv6

• https://developers.google.com/speed/public-dns/docs/using

2001:4860:4860::8888
2001:4860:4860::8844

Add Digital Society Switzerland

• https://res3.digitale-gesellschaft.ch/
• https://github.com/DigitaleGesellschaft/DNS-Resolver#technical-information--configuration-how-tos
• https://www.digitale-gesellschaft.ch/dns/
• https://www.digitale-gesellschaft.ch/.well-known/security.txt

[yubiuser]

Seems to be online again

[weyCC81]

The main site, yes, but not the subsite's (menu).

Web: partly offline since summer 2024 apparently

• http://web.archive.org/web/20240518031905/https://dns.watch/why
• http://web.archive.org/web/20231223232256/https://dns.watch/contact
• http://web.archive.org/web/20240619180353/https://dns.watch/contact

Donate: last transaction=11/24/2023

• https://www.blockchain.com/explorer/addresses/btc/1DNSaFkH4a5mexQvn3oWFmdwH7VNodepLw

This address has transacted 26 times on the Bitcoin blockchain. It has received a total of 0.16519136 BTC $16,052.65 and has sent a total of 0.16519136 BTC $16,052.65 The current value of this address is 0.00000000 BTC $0.00.

E-Mail:

• dnswatch^pm.me

DNS Test to "google.com":

Who is running this service?

[yubiuser]

When did you noticed the site is down?
Currently, the dns server seems to have a some issues too. Maybe they have some high load

nanopi@nanopi:/$ dig google.com @84.200.69.80
;; communications error to 84.200.69.80#53: timed out

; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> google.com @84.200.69.80
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65374
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		2	IN	A	142.250.184.174

;; Query time: 19 msec
;; SERVER: 84.200.69.80#53(84.200.69.80) (UDP)
;; WHEN: Thu Jan 02 18:25:10 CET 2025
;; MSG SIZE  rcvd: 55

[github-actions]

This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.

[phit]

still broken, not a fan of offering a dns server by default with no working website or privacy policy

[mwoolweaver]

seems ok here. got this on the first try.

movies@blockbuster:~$ dig google.com @84.200.69.80

; <<>> DiG 9.20.0-2ubuntu4-Ubuntu <<>> google.com @84.200.69.80
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22465
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		282	IN	A	142.250.184.174

;; Query time: 152 msec
;; SERVER: 84.200.69.80#53(84.200.69.80) (UDP)
;; WHEN: Wed Feb 05 14:30:28 CST 2025
;; MSG SIZE  rcvd: 55

[yubiuser]

Mhh... it timed out for me 3 times in a row. Service seems unreliable.

Transferring to FTL repo, as in v6 the default servers are handled from there.

[phit]

it seems to time out basically every time it doesn't have the request in cache

[rdwebdesign]

Here 84.200.69.80 worked correctly 3 times in a row and failed in a forth test (after a fast succession of attempts).
84.200.70.40 failed half of the attempts.

[DL6ER]

I tried dns.watch from a location close to Frankfurt (Germany) and get responses for both servers within 15 - 30 msec but also about 50% error rate. For comparison: ping de-cix.net is between 2 - 3 msec.

What do you suggest for Google IPv6? We already use the IP addresses you quoted (even when not in abbreviated form).