162.76 Mbit/s 74.408 ms Germany, Berlin (DNS:NET) 116.65 Mbit/s 111.58 Mbit/s 91.629 ms Spain, Madrid (MasMovil) 195.38 Mbit/s 159.48 Mbit/s 91.902 ms Italy, Rome (Unidat

Can’t we just choose a different dns while setting it up or set new one by modifying the .conf file ?

Personally done some modifications to Nyr’s script to use different DNS servers - it works perfectly

(Quote)

(Quote)

This is a network status graph for the time it takes to do an authoritative DNS resolution by this server from four locations every 3 minute for yesterday. Top graph is IPv4, bottom graph is IPv6.

* Reverse DNS Available (On Request)

(Quote)

uploaded it to the new host, and redirected the DNS to point there instead, and it's started working almost right away. I can get the SSL cert provisioned for the new site once DNS finishes propogati

(Quote)

Another way to restart after dns is available, combined with @yoursunny can be like this:

(Quote)

@yoursunny Noted on why dns reset back to "127.0.0.53". Thanks for the link.

(Quote)

(Quote)

If you do this, the DNS in /etc/resolv.conf would still be 127.0.0.53, but the DNS queries are forwarded to the configured DNS servers, as well as those received via DHCP (if you have KVM and enable D

(Quote)

First operate sudo systemctl stop systemd-resolved After editing and saving DNS= and FallbackDNS= in /etc/systemd/resolved.conf, (ensure it is ipv6) run this command sudo systemctl start systemd-resol

@Chandler, FYI...I'm using ssh to login. Everytime i do a reboot the dns reset back to "127.0.0.53". I submitted a ticket since 12/25/2022 on this issue and until today it's not solv

If you reboot through the control panel, it will reset to the system default dns, you can prevent the dns reset by just typing "reboot" in the system.