On Mon, Apr 13, 2015 at 11:10 AM, Evan Hunt e...@isc.org wrote:
On Mon, Apr 13, 2015 at 11:05:05AM -0700, Frank Even wrote:
...and where could I find info on what is stored in ADB and any other
particular items that flushname might not deal with? That's where my
frustration largely is, that I
On Sat, Apr 11, 2015 at 6:49 AM, Tony Finch d...@dotat.at wrote:
There was a bug in 9.9 and earlier that rndc flushtree only flushed the main
cache, not adb or bad cache. This was fixed in 9.10 - see item 3606 in the
CHANGES file.
...and where could I find info on what is stored in ADB and
On Mon, Apr 13, 2015 at 11:05:05AM -0700, Frank Even wrote:
...and where could I find info on what is stored in ADB and any other
particular items that flushname might not deal with? That's where my
frustration largely is, that I can't find clear documentation on this
point.
I believe rndc
On Mon, Apr 13, 2015 at 11:17:41AM -0700, Frank Even wrote:
I have to apologize for that. I'd still definitely be curious to know
what info is stored in the ADB though since according to the docs ADB
was never intended to be flushed with a flushtree (although that has
now apparently been
There was a bug in 9.9 and earlier that rndc flushtree only flushed the main
cache, not adb or bad cache. This was fixed in 9.10 - see item 3606 in the
CHANGES file.
Tony.
--
f.anthony.n.finch d...@dotat.at http://dotat.at
___
Please visit
In this particular case, when the issue came to me, the
name servers for the domain were able to return the result with no
problems, other caching servers throughout the company had no issues,
but this group of servers that apparently had tests run against the
domain prior to it being fully setup
On Thu, Apr 9, 2015 at 1:48 PM, Matus UHLAR - fantomas
uh...@fantomas.sk wrote:
On 09.04.15 13:25, Frank Even wrote:
Is there any place I can look to get a definitive answer in what cases
flushname will and will not work?
it will work if you have old entries in the cache.
that will NOT
On 09.04.15 13:25, Frank Even wrote:
Is there any place I can look to get a definitive answer in what cases
flushname will and will not work?
it will work if you have old entries in the cache.
that will NOT help you if any of the servers that are supposed to be
authoritative for a domain will
Is there any place I can look to get a definitive answer in what cases
flushname will and will not work? I've been digging around in lists
and docs and can't seem to find any definitive answers. I've been
having odd troubles clearing a name from a cache and after even
clearing the name and the
On Wed, Dec 10, 2014 at 3:36 AM, Matus UHLAR - fantomas uh...@fantomas.sk
wrote:
On 09.12.14 21:36, Frank Bulk wrote:
Perhaps it wasn't NXDOMAIN -- I didn't capture the output. But there
definitely was not answer. The institution only has two authoritative
nameserver entries, both pointing
On 09.12.14 21:36, Frank Bulk wrote:
Perhaps it wasn't NXDOMAIN -- I didn't capture the output. But there
definitely was not answer. The institution only has two authoritative
nameserver entries, both pointing to the same IP, so all it was all down.
In any case, why doesn't flushing the name
Next time I'll dump the db.
Frank
-Original Message-
From: bind-users-boun...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of Matus UHLAR -
fantomas
Sent: Thursday, December 11, 2014 10:32 AM
To: bind-users@lists.isc.org
Subject: Re: rndc flushname not working
On 09.12.14 21:36, Frank Bulk wrote:
Perhaps it wasn't NXDOMAIN -- I didn't capture the output. But there
definitely was not answer. The institution only has two authoritative
nameserver entries, both pointing to the same IP, so all it was all down.
In any case, why doesn't flushing the name
Our ISP operations are running a mixture of 9.7.3 and 9.8.4 on several
Debian servers and we've noticed that rndc flushname doesn't work many
times.
This weekend we had a local institution whose own authoritative DNS servers
[all of them] were offline for 48+ hours and so there were several
Nameservers being down does not result in NXDOMAIN responses. I
suspect that some of the auth servers were producing NXDOMAIN
incorrectly. Flushing the name won't help in those cases.
In message 001001d01429$1c857f70$55907e50$@iname.com, Frank Bulk writes:
Our ISP operations are running a
15 matches
Mail list logo
