Hi Ondrej,
On Wed, Apr 06, 2016 at 03:36:11PM +0200, Ond??ej Surý wrote:
no, we don't have such option. DENIC should fix
their interface as their checks are broken.
I never said that DENIC's checks are very *useful* (or that we're worried
about it) - but that's how I came to know about it.
DNS is indeed case insensitive and Knot DNS does the
unification for performance reasons.
One of the other values of unifying the case is a DNS compression making the DNS
responses smaller. You wouldn't be able to use DNS compression if you have
inconsistent case through the zone.
Well, we do have consistent casing - uppercase S and N, it's just that
knot is the odd one here, causing recursors to see mixed-case or
lowercase-only results, depending on which authority they are asking.
I'm a bit frustrated to hear that, because "not interfere with the stuff
I put into a zone file, unless I authorize software to do it" is indeed
important to us - so it's "back to bind" time for now.
I can see the compression argument (and surprisingly it seems to reflect
in the traffic volume of the machine - though that might be due to other
optimizations in knot, not just case folding) - but since the difference
between bind and knot is only about 10-20 Gbytes per month, this is not
an issue of utmost importance for us.
(The "lookup performance" issue I can also see, but this should not
affect "responses shipped" - like in a SOA or PTR record)
thanks for clarification,
Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279