Webdock uses Google DNS with Cloudflare as backup

Last updated: April 4th 2021

architecture-buildings-city-fb.jpg

After much recent testing we have changed our default DNS servers in our network configuration for our VPS servers to use Google as the primary DNS (8.8.8.8) and Cloudflare (1.1.1.1) as the secondary.

We used to have Cloudflare as both our primary and secondary resolver on all our VPS servers but due to recent issues with certain lookups via. Cloudflare we have decided to make Google our primary and Cloudflare our backup. Although Google DNS can in some cases be 20-40ms slower than Cloudflare, in other cases Cloudflare chokes up and takes up to several seconds to respond with a proper reply. 

Due to the greater stability of the Google DNS - at least for the moment - we have switched over to them now and moving forward we will continue with this hybrid approach. Meaning, having a primary DNS server set from one provider and the backup from another - which should result in much better uptime and connectivity in case one or the other provider is having a bad day.

Please note: This change only affects new servers (created after April 4th 2021). Any old servers will still use Cloudflare as their primary and secondary DNS resolver.

If you want to change over to Google as your primary DNS resolver with Cloudflare as the backup, you can do so by editing /etc/netplan/100-webdock.yaml where you change the lines shown in red below and rebooting your server:

################################# WEBDOCK ##################################
network:
  version: 2
  renderer: networkd
  ethernets:
    eth0:
      addresses:
        - xx.xx.xx.xx/22
        - xx:xx:xx:xx:xx:xx:xx:xx/48
      gateway6: xx:xx:xx::xx
      nameservers:
        addresses:
          - 8.8.8.8
          - 1.1.1.1
          - 2001:4860:4860::8888
          - 2606:4700:4700::1111
      routes:
        - to: 0.0.0.0/0
          via: xx.xx.xx.xx
################################## WEBDOCK #################################

 

We use cookies. Please see our Privacy Policy.