Some more information that I found:

The option: https://www.knot-dns.cz/docs/1.6/html/reference.html#zones-list-of-zone-semantic-checks

Doesn't not seem to work for AXFR on my setup, each zone that I need to transfer has:

    xfr-in master;
    notify-in master;
    update-in master;

Declared and in the main config:

remotes {
  master { address 127.0.0.1@53;  }
}

zones {
    ...
    semantic-checks off;
}

But I still get warnings and transfer failed while doing the AXFR transfer.

On Tue, Jun 30, 2015 at 12:44 PM, Filipe Cifali <cifali.filipe@gmail.com> wrote:
My clients broke their own zones, sadly when I first started the sysadmins already made it to "function" this way.

Freedom to the users, doom to the admins.

By making them compliant to RFC1912 I would potentially take off their sites down and that's not an option atm.


On Tue, Jun 30, 2015 at 12:37 PM, Andreas Olsson <andreas@arrakis.se> wrote:
tis 2015-06-30 klockan 12:14 -0300 skrev Filipe Cifali:
> I'm migration from PowerDNS using AXFR and some of the domains fall on
> Section 2.4 having CNAME on top domains.
>
> Is there a way to ignore the warning and receive the query?
> ...

Out of curiosity, why don't you simply fix the broken zones?

// Andreas

_______________________________________________
knot-dns-users mailing list
knot-dns-users@lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users




--
[ ]'s

Filipe Cifali Stangler



--
[ ]'s

Filipe Cifali Stangler