Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


what dns do you use for resolve.conf - Page 2
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

what dns do you use for resolve.conf

2»

Comments

  • hide1hidehide1hide Member
    edited October 2019
    nameserver 1.1.1.1
    nameserver 8.8.8.8
    nameserver 9.9.9.9
    nameserver 64.6.65.6
    nameserver 199.85.126.20
    nameserver 8.26.56.26
    nameserver 74.82.42.42
    
  • @hide1hide said:
    nameserver 1.1.1.1
    nameserver 8.8.8.8
    nameserver 9.9.9.9
    nameserver 64.6.65.6
    nameserver 199.85.126.20
    nameserver 8.26.56.26
    nameserver 74.82.42.42

    You realize that only the first three will be considered and that the last four are superfluous, right?

    Thanked by 1Ole_Juul
  • I prefer to use OpenDNS 208.67.222.222 and 208.67.220.220

  • loydloyd Member
    edited October 2019

    CloudFlare 1.1.1.1 on the WAN router and WAN router on all intranet nodes

    If possible, I stay away from anything Google, they have trouble following specs, make their own rules and lot of their software has bugs that have lingered for years, common excuse is you did not pay for it so suck it up. Used to have 8.8.8.8 and 8.8.4.4 on all PCs and raspberies, but run into some weird hair pulling glitch which disappeared when switching to CF or OpenDNS. Ironically, some ISPs use Google DNS as their upstream authority so keep that in mind when using straight DHCP on the main router.

  • Some local resolvers that don’t log from OpenNic, otherwise 9.9.9.9.

  • FHRFHR Member, Host Rep

    We run our own caching forwarders for customer VMs. Forwarding queries to 9.9.9.10 and 2620:fe::10 (Quad 9), 4.2.2.2 (Level 3) and 74.82.42.42 (HE).

    You won't find any Cloudflare there :wink:

    Thanked by 1uptime
  • I don't use dns, it's centralized.
    I just enter random IP numbers and if it hits, it hits.

    Thanked by 4ITLabs uptime grep mrTom
  • DPDP Administrator, The Domain Guy

    Just Google's DNS most of the time, on most of my servers.

  • my own

    Thanked by 3Ole_Juul uptime ras07
  • FHR said: 4.2.2.2 (Level 3)

    The Level 3 resolvers will redirect to a search engine instead of returning NXDOMAIN for non existent domains. Can make it hard to identify domain typos or validate domains exist or other unexpected things for your customers. Food for thought.

    ~$ dig fakefakieafdsfa.com @4.2.2.2 +short
    23.217.138.108
    23.202.231.167
    ~$ dig fakefakieafdsfa.com @9.9.9.10 +short
    ~$
    
    Thanked by 3uptime hanoi rm_
  • HackedServer said: The Level 3 resolvers will redirect to a search engine instead of returning NXDOMAIN for non existent domains.

    Many DNS servers can filter those bogus IP addresses, for example, dnsmasq has the --bogus-nxdomain option.

  • Related, a recent StackExchange discussion on the Cloudflare DNS.

    https://webapps.stackexchange.com/questions/135222/why-does-1-1-1-1-not-resolve-archive-is/135223

    Thanked by 1uptime
  • 1.0.0.1 or 8.8.8.8 8.8.4.4 works fine for most areas...

  • DNS caching with Pihole on local network, so 192.168.x.xx and using cloudflare on pihole.

  • 8.8.8.8

Sign In or Register to comment.