In message <5382eb30.6040...@ripe.net>, Anand Buddhdev writes:
> On 26/05/2014 01:53, Mark Andrews wrote:
>
> Hi Mark,
>
> > Actually that isn't the mistake as they are both run through
> > dns_name_fromtext which will normalise them before comparison.
>
> I didn't know that. Does this mean tha
On 26/05/2014 01:53, Mark Andrews wrote:
Hi Mark,
> Actually that isn't the mistake as they are both run through
> dns_name_fromtext which will normalise them before comparison.
I didn't know that. Does this mean that dots and dashes are equivalent
or irrelevant in tisg key names?
Regards,
Anan
In message <538274b9.6070...@ripe.net>, Anand Buddhdev writes:
> On 25/05/2014 16:58, micah wrote:
>
> > zone "example.net" {
> > type master;
> > allow-transfer { key tsig.key.; };
>
> Here's your mistake. You've written tsig.key, whereas your key is called
> tsig-key. Those nam
On 25/05/2014 16:58, micah wrote:
> zone "example.net" {
> type master;
> allow-transfer { key tsig.key.; };
Here's your mistake. You've written tsig.key, whereas your key is called
tsig-key. Those names don't match.
> also-notify { ip.address.here.x; };
> file "/
I suggest that you stop obfuscating the details. Errors like this are
almost always in the details. Hide the secret ('x' it out) but nothing
else. The spelling of key names is important (they must match exactly)
as are the IP addresses.
Did you reload both servers after updating them. Did you
5 matches
Mail list logo
