On 12/8/18 5:53 PM, Samuel Sieb wrote:
On 12/8/18 8:23 AM, sean darcy wrote:
> I'm running a DNS server (unbound) on a VOIP server. It's crucial that
> I can always resolve addresses, even if it's slower. Now DNS1 is set
> to 127.0.0.1, peerdns no. Giving:
How does the local DNS do the resolving. Why is it slower?
> What I want is:
> nameserver 127.0.0.1
> nameserver <whatever dhcp gives>
This will not work the way you are expecting. Resolving will always go
to the first one unless it doesn't respond. In that case it will go to
the second one, but that will be slow because every request has to
timeout on the first one before that.
My local server - unbound - works great. Never a problem, almost.
Sometimes there's a problem on reboot, and unbound doesn't start. For
that very rare event, I'd like a backup - even if it's very slow. The
VOIP server - asterisk - will shut down if it can't resolve ip addresses
within 4 or 5 minutes. And then I have a real problem.
I'd like to avoid a single point of failure, even if unlikely.