At about Monday, September 16, 2013 6:54 PMDan McDaniel wrote:
>querying the
>failed fedora NS. Then it came back with a not found. My company's
>networking group said it's the fault of the bad fedora NS.
If the fedora NS had returned SERVFAIL or if it was not reachable,
your company's NS WOULD
On 17 September 2013 02:54, Dan McDaniel wrote:
> My question is shouldn't our nameservers try another fedora NS in order
> to resolve the name? If not what good is it for fedora to have multiple
> nameservers? Or am I misunderstanding how this should work?
So this would really depend on the resp
Here's the scenario. Last week one of the Fedora nameservers was not
responding so I was having trouble resolving fedoraproject.org.
Apparently my company's nameserver was sending out the request,
receiving the list of nameservers from the root and then querying the
failed fedora NS. Then it came
Hi,
I have an instance of named (9.9.3-P1-ESV) with a 150M zone (unsigned) and
max-journal-size 100M with frequent dynamic updates (about 1 every second).
Occasionally CPU usage for the named process will spike up to maximum and named
becomes slow to respond to queries; some even time out. Thi
4 matches
Mail list logo