Hi all :-)
I've a quad core 2.4Ghz with standard italian DSL
I tested BIND with either forwarder activated and disactivated
forwarders {
8.8.8.8; 8.8.4.4;
};
without forwarder, using dig command, "query time" only on some domains
(I tested italian domains - I live
On 20.09.16 12:29, Pol Hallen wrote:
I've a quad core 2.4Ghz with standard italian DSL
I tested BIND with either forwarder activated and disactivated
forwarders {
8.8.8.8; 8.8.4.4;
};
without forwarder, using dig command, "query time" only on some
domains (I tested i
Am 20.09.2016 um 12:29 schrieb Pol Hallen:
without forwarder, using dig command, "query time" only on some domains
(I tested italian domains - I live in Italy) is 350-800ms, with
forwarder almost always is less 100ms (!)
I'd like have my BIND (no forwarder) that works for my lan :-)
which is
what happend if you leave it working (without forwarders) for some time?
BIND should cache frequently used data and provide them quickly.
I don't know. I start now testing without forwarders and tonight I see
when you use google forwarder, the main difference is that most of those
data are pro
On 20.09.16 15:03, Pol Hallen wrote:
what happend if you leave it working (without forwarders) for some time?
BIND should cache frequently used data and provide them quickly.
I don't know. I start now testing without forwarders and tonight I see
when you use google forwarder, the main differe
Am 20.09.2016 um 15:03 schrieb Pol Hallen:
what happend if you leave it working (without forwarders) for some time?
BIND should cache frequently used data and provide them quickly.
I don't know. I start now testing without forwarders and tonight I see
when you use google forwarder, the main
just leave bind running for some time.
:-)
with 9.10, leave prefetch on and see...
I've 9.9.5 version on debian stable :-/
thanks
Pol
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users ma
On 16 September 2016 at 11:12, project722 wrote:
> I have an interesting problem. I started noticing that when I do a dig
> +trace against one of the domains we are authoritative for, we get errors
> from our nameservers for "Bad Referral" and you can see where it forwarded
> the request back up
with 9.10, leave prefetch on and see...
On 20.09.16 15:12, Pol Hallen wrote:
I've 9.9.5 version on debian stable :-/
so simply leave BIND running and see if it's better tomorrow...
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail
I've reverted my configuration back to before we started using views. But,
if this was a delegation issue, wouldn't we expect to see it regardless of
using views or not? Works fine without views.
On Tue, Sep 20, 2016 at 8:58 AM, Matthew Pounsett
wrote:
>
>
> On 16 September 2016 at 11:12, projec
On 20 September 2016 at 12:50, project722 wrote:
> I've reverted my configuration back to before we started using views. But,
> if this was a delegation issue, wouldn't we expect to see it regardless of
> using views or not? Works fine without views.
>
It's entirely possible you introduced some
Is there a way to add forwarders for specific zones without a restart?
Everything I've read seems to indicate an "rndc reconfig" or an "rndc
reload" should take care of this, but they do not. I add forwarders to
"named.conf" and neither will load the new forwarded zone until I do a full
daemon res
On 2016-09-21 02:40, Frank Even wrote:
Is there a way to add forwarders for specific zones without a restart?
Everything I've read seems to indicate an "rndc reconfig" or an "rndc
reload" should take care of this, but they do not. I add forwarders
to "named.conf" and neither will load the new f
The basics are fine. BIND just doesn't load newly added forwarded zones,
period. It also kind of lies in the output:
Sep 20 17:57:48 host01 named[26453]: reloading configuration succeeded
Sep 20 17:57:48 host01 named[26453]: any newly configured zones are now
loaded
...except they're not. Thus
I have a DNS server (which is both forwarder and authoritative NS) and I see
this odd behavior locally on the host:
dig @localhost # returns immediately with right response
dig @ # returns sometimes, timesout most of
the time
I have allow-query {any;} in BIND config and the above i
15 matches
Mail list logo
