/ Register

Join the community today
Become a Member

Sysadmin Alternative Public DNS resolvers from Google 8.8.8.8 and 8.8.4.4

Discussion in 'System Administration' started by eva2000, Jul 30, 2015.

Tags:
Previous Thread Next Thread
Loading...
  1. Jul 30, 2015 #1
    eva2000

    eva2000 Administrator Staff Member

    34,598
    7,653
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +11,770
    Local Time:
    5:22 PM
    Nginx 1.15.x
    MariaDB 5.5/10.x
    I Just came across a DNS resolver issue with some of my VPSes which by default set in /etc/resolv.conf the following Google public dns

    Code:
    nameserver 8.8.8.8
nameserver 8.8.4.4
    However, I couldn't ping out anywhere, so had to try alternative public dns which worked.

    I used Comodo Secure DNS Comodo Secure DNS, Managed DNS Service, Secure DNS Provider

    so
    Code:
    nameserver 8.26.56.26
nameserver 8.20.247.20
    So something like

    Code:
    options rotate
options timeout:1
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 8.26.56.26
nameserver 8.20.247.20
    Note this won't help with ping tests out as ping looks up the first instance and exits so never gets to try further down the rotation.

    Just a heads up for folks :)
     
    Last edited: Jul 30, 2015
  2. Jul 30, 2015 #2
    rdan

    rdan Premium Member Premium Member

    4,195
    1,014
    113
    May 25, 2014
    Ratings:
    +1,438
    Local Time:
    3:22 PM
    Mainline
    10.2
    I encounter this when I change CentOS 7.1 default hostname on Linode :D
     
    • Informative Informative x 1
  3. Jul 30, 2015 #3
    eva2000

    eva2000 Administrator Staff Member

    34,598
    7,653
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +11,770
    Local Time:
    5:22 PM
    Nginx 1.15.x
    MariaDB 5.5/10.x
    well for me the vpses had been running for a few weeks without problem so only happened just today so probably a glitch for 8.8.8.8 for a while
     
Previous Thread Next Thread
Loading...
..

.