Hi
I have been experience DNS resolutions problems these past few days, if
i run nslookup i get this error:
;; connection timed out; no servers could be reached
with dig +trace i get:
; <<>> DiG 9.6-ESV-R1 <<>> @ espn.com +trace
; (1 server found)
;; global options: +cmd
;; connection timed o
I've configured bind-9.7.1 with DNSSec and stored the keys online, to
allow dynamic updates via nsupdate. Here are the relevant bits from my
named.conf:
options {
...
dnssec-enable yes;
directory "/var/named/db";
key-directory "/var/named/keys";
...
};
key
If you really do have such a small pipe (with your email address I assume
Sweden. I didn't think Swedes even knew there were link types other than
fibre ;) )then perhaps you're throttling it to the point where your NTP sync
drops off.
Options:
Perhaps try some traffic shaping on the link. IXFR or
Hi,
The size of the zone should not be that much of a matter if you use
IFXR. Aside from that, did you ever consider using another mechanism for
synchronization, like rsync or lzmaing the zone and transferring it via
your protocol of choice?
Then again, why would one have a TLD coloc on a 256kbps
Hello,
On ons, 2010-07-07 at 14:41 +0200, Tom Schmitt wrote:
> Original-Nachricht
> > Datum: Wed, 07 Jul 2010 13:13:45 +0200
> > Von: Niklas Jakobsson
> > An: bind-us...@isc.org
> > Betreff: bind says \'clocks are unsynchronized\' but they are not
>
> > Hello,
> >
> > I have s
Original-Nachricht
> Datum: Wed, 07 Jul 2010 13:13:45 +0200
> Von: Niklas Jakobsson
> An: bind-us...@isc.org
> Betreff: bind says \'clocks are unsynchronized\' but they are not
> Hello,
>
> I have some problems with our bind servers complaining that 'clocks are
> unsynchronize
Hello,
I have some problems with our bind servers complaining that 'clocks are
unsynchronized' when doing zone transfers with TSIG. The problem is the
clocks are correct, synced with ntp and everything.
The problems seems to occur mostly on zone transfers that take a long
time (ie. hours).
Any
7 matches
Mail list logo
