Did you compile both openssl and bind or are you using a prebuilt binary?
There are (apparently) problems with OpenSSL 1.0.2 on the 32 bit Solaris
10 platform. This was discussed on the openssl-users mailing list
a few months ago. The "fix" was building with an openssl 1.0.1
version on that pla
All
It occurred to me that you may need more info to assist me the logs show the
following:
Jul 23 15:55:11 nit-dns2 named[20169]: [ID 873579 daemon.notice] starting BIND
9.10.2-P2 -t /nithr -u nithr -d 2 -f
Jul 23 15:55:11 nit-dns2 named[20169]: [ID 873579 daemon.notice] built with
'--prefix=
I am having issues with bind failing to start due to a crypto failure when I
compile with the --with-openssl option when I have openssl version 1.0.2d or
1.0.2c
Is anyone aware of any compatibility issues between bind and openssl version
1.0.2? I have no issues when I use openssl version 0.9.8z
On Fri, Jul 24, 2015 at 11:52 AM, Mark Elkins wrote:
> On Fri, 2015-07-24 at 15:44 +, Managed Pvt nets wrote:
> >
> >
> > On 24/07/2015 5:05:24 PM, "Alan Clegg" wrote:
> >
> > > Possible problems:
> > >Mismatched keys.
> > >Mismatched key names.
> > >Mismatched clocks.
> >
> > Mo
On Fri, 2015-07-24 at 15:44 +, Managed Pvt nets wrote:
>
>
> On 24/07/2015 5:05:24 PM, "Alan Clegg" wrote:
>
> > Possible problems:
> >Mismatched keys.
> >Mismatched key names.
> >Mismatched clocks.
>
> Most likely mismatched key. I have to figure out how to make sure my
>
On Fri, 2015-07-24 at 11:05 -0400, Alan Clegg wrote:
> Possible problems:
>Mismatched keys.
>Mismatched key names.
>Mismatched clocks.
Yes - running some sort of Time Synchronisation is often overlooked.
Check: Simultaneously run "date" on both machines - must be within 5
minutes of ea
On 24/07/2015 5:05:24 PM, "Alan Clegg" wrote:
Possible problems:
Mismatched keys.
Mismatched key names.
Mismatched clocks.
Most likely mismatched key. I have to figure out how to make sure my
master does not require TSIGs and my slave does not try to use them.
___
On 24/07/2015 5:03:12 PM, "John Miller" wrote:
If you're not intending to use TSIG, make sure your master doesn't
require it and that your slave doesn't try to use it for its AXFRs.
I think this is what I have to figure out to do.
___
Please v
Possible problems:
Mismatched keys.
Mismatched key names.
Mismatched clocks.
On 7/24/2015 10:52 AM, Managed Pvt nets wrote:
> Hi All,
>
> I have recently built a server to act as a secondary / slave for my
> zones. Built on Debian 8.1 and running BIND 9.9.5. On trying to
> transfer zone
On Fri, Jul 24, 2015 at 10:52 AM, Managed Pvt nets wrote:
> Hi All,
>
> I have recently built a server to act as a secondary / slave for my zones.
> Built on Debian 8.1 and running BIND 9.9.5. On trying to transfer zones
> from my master I am getting this error here, what could I be missing:
>
>
Hi All,
I have recently built a server to act as a secondary / slave for my
zones. Built on Debian 8.1 and running BIND 9.9.5. On trying to transfer
zones from my master I am getting this error here, what could I be
missing:
===
Jul 24 15:33:55 huffer named[493]: zone myzonename.co.zw/IN: re
11 matches
Mail list logo
