long FQDN resolution

DEMBLANS Mathieu demblans.m at mipih.fr
Thu May 15 14:31:40 UTC 2025


Hello,
I have a question about mecanism for requests of long subdomains FQDN.
Our DNS, which is in recursive configuration, split long fqdn request with subdomains requests like :

Original request from the client to our recursive DNS : A a.b.c.d.example.com

Requests done by our DNS to the domain example.com NS:
A  _.c.d.example.com
A _b.c.d.example.com
A a.b.c.d.example.com

Is it a normal behaviour ?

This is only done for 4 levels domains (a.b.example.com for example) and more, not < normal > fqdn (ex : www.example.com).
What part of the configuration manage this mecanism ?
Is this really usefull ?

It is problematic for DNSBL requests because it generate a lot of useless requests and this kind of service look at the number of requests done (usage policy):

[cid:image002.png at 01DBC5B3.192E1570]




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20250515/a212bfac/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 32263 bytes
Desc: image002.png
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20250515/a212bfac/attachment-0001.png>


More information about the bind-users mailing list