On 10Nov23, Paul Wouters apparently wrote:
> > I'd like to write a draft that updates RFC 9156 by describing situations
> > like this that caches could recognize and avoid useless churn, added to
> > section 2.3 which already suggests special casing underscored labels.
>
> Couldn't the RBL's add an underscore in their base zone name to trigger
> the special casing in 9156? That would not require a new RFC and
> perhaps might not require code updates?
That doesn't help ip6.arpa tho.
I must admit I was a bit surprised when I first spun up a custom reverse auth
to find that
nearly 80% of ip6.arpa queries were qmin walking with only 20% asking for the
ultimate
PTR. Here's a typical log entry for one query:
q=A/4.3.2.1.0.0.0.0.0.2.2.5.e.c.f.f.f.f.f.f.f.ip6.arpa.
p=36142 id=27861 sz=198/1232 C=0/1/1 Trunc-qmin
q=A/1.0.0.0.0.4.3.2.1.0.0.0.0.0.2.2.5.e.c.f.f.f.f.f.f.f.ip6.arpa.
p=53007 id=34561 sz=208/1232 C=0/1/1 Trunc-qmin
q=A/1.0.0.0.2.1.0.0.0.0.4.3.2.1.0.0.0.0.0.2.2.5.e.c.f.f.f.f.f.f.f.ip6.arpa.
p=62639 id=57771 sz=218/1232 C=0/1/1 Trunc-qmin
q=A/3.1.0.0.0.2.1.0.0.0.0.4.3.2.1.0.0.0.0.0.2.2.5.e.c.f.f.f.f.f.f.f.ip6.arpa.
p=9742 id=43025 sz=220/1232 C=0/1/1 Not PTR
q=PTR/3.1.0.0.0.2.1.0.0.0.0.4.3.2.1.0.0.0.0.0.2.2.5.e.c.f.f.f.f.f.f.f.ip6.arpa.
p=34942 id=48483 sz=211/1232 C=1/0/1 DB:autoreverse
In effect qmin causes this server to see 5 times as many queries as it might
otherwise get.
Mark.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
