localhost name lookup

[Greg Choules]

> On 24 Jan 2025, at 19:07, Lee <ler762 at gmail.com> wrote:
> 
> On Mon, Jan 20, 2025 at 4:55 AM Petr Špaček wrote:
>> 
>> On 15. 01. 25 19:55, Lee wrote:
>>> On Wed, Jan 15, 2025 at 11:55 AM Ondřej Surý wrote:
>>>> On 14. 1. 2025, at 16:56, Lee <ler762 at gmail.com> wrote:
>>>> 
>>>> In other words, should I submit a bug report to the Debian bind
>>>> maintainers or ISC?
>>>> 
>>>> 
>>>> With both my ISC and Debian hats on, I am going to be very frank
>>>> and say this has a very low priority, so unless you actually want to
>>>> work on this and submit a solid correct patch with a good reasoning,
>>>> there's probably nobody that is going to work on this.
>>> 
>>> I appreciate the honesty, but I think I'm missing something?
>>> 
>>> The good reasoning part would be quoting the RFC and the solid correct
>>> patch would be stripping out everything except the two line change I
>>> made to my db.local in the original post.
>> 
>> Unfortunately not quite, BIND does not ship with any zone files.
> 
> Really?!  I installed BIND on windows however long ago when it was
> supported on Windows and it came with a db.local that looked identical
> to the one that came with Debian.

Certainly for the last quite a lot of years there hasn't been a hint zone file - whatever it might be called - shipped with BIND, if ever: there are too many releases to search through.
The current (at the time of release) set of root servers are contained in the file rootns.c, but this is definitely not a zone file, just the place BIND gets its built-in hints from.
I would think that, if a file called db.local, db.hint, db.root or whatever does exist, it is someone else who created it.

> 
>> It
>> would have to be code change to implement
>> https://datatracker.ietf.org/doc/html/rfc6761#section-6.3
>> inside BIND codebase, something similar to empty zones.
>> 
>> (Or, refactor codebase to pull all special zones from files, which is
>> ... well ... somewhat larger change.)
>> 
>> Perhaps in packages it would be easier (albeit limited impact), but I
>> don't maintain any of them myself.
>> 
>>> Is anything else required other than formatting the [implicit] change
>>> as a patch?
>>> 
>>>> The itch to scratch here isn't particularly bothering.
>>> 
>>> I understand.  Where do I submit the patch?
>> 
>> Please start with
>> https://gitlab.isc.org/isc-projects/bind9/-/blob/main/CONTRIBUTING.md
> 
> With db.local not being in the ISC code base it seems like I should be
> submitting the bug report to Debian.
> But with Ondřej Surý saying
>>>> With both my ISC and Debian hats on
> 
> approval seems unlikely.
> 
> I appreciate all your help but I've taken up enough of everyone's
> time; I'll quit now.
> 
> Thanks,
> Lee
> -- 
> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
> 
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users