Project

General

Profile

Actions

Bug #9514

closed

DNS servers

Added by Dallas Haselhorst almost 5 years ago. Updated almost 5 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
05/11/2019
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

Right now, the query order for DNS servers can vary based on query times. Using DNS from multiple providers is great to prevent outages, however, it isn't as helpful when mixing/matching DNS queries where some DNS providers utilize domain blacklisting. Case in point, it would be great to use Quad9 for primary and secondary DNS and only use Cloudflare if there is a problem with Quad9. This could be performed by either artificially slowing the DNS for Cloudflare to ensure it is always 3rd or by creating an "only use in case of failure" option for Cloudflare if the primary/secondary DNS are both down.

Actions #1

Updated by Jim Pingle almost 5 years ago

  • Status changed from New to Not a Bug

The DNS Resolver (Unbound) doesn't work that way.

You can do that in the DNS forwarder by telling it to query sequentially instead of in parallel. If you need assistance with that, post on the forum.

Actions

Also available in: Atom PDF