On 1/24/25 2:07 PM, Lee wrote:
On Mon, Jan 20, 2025 at 4:55 AM Petr Špaček wrote:
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 on
On 1/24/25 17:09, phil via bind-users wrote:
ftr ubuntu also ships bind with a db.local file
I wonder if we're dancing around what upstream from ISC ships vs what
distros create therefrom and ship.
I'll have to check my copies of the venerable BIND book to be sure, but
I believe that it and
I already told you that the db.local comes from Debian when you emailed me
privately. Yet, you continue to not listen what other people are saying.
When I said:
> 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
On 25/1/25 10:01, Greg Choules wrote:
I just looked in the source for 9.0.0, released nearly 25 years ago,
to see what was there because I was curious. There is no file called
“db.local": here’s the link if you want to check for yourself:
https://downloads.isc.org/isc/bind9/9.0.0/ Every relea
> On 24 Jan 2025, at 21:32, Lee wrote:
>
> On Fri, Jan 24, 2025 at 3:27 PM Greg Choules wrote:
>>
>>
>>> On 24 Jan 2025, at 19:07, Lee 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 S
On Fri, Jan 24, 2025 at 3:27 PM Greg Choules wrote:
>
>
> > On 24 Jan 2025, at 19:07, Lee 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 wrot
> On 24 Jan 2025, at 19:07, Lee 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 wrote:
In other words, should I submit a bug report to the D
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 wrote:
> >>
> >> In other words, should I submit a bug report to the Debian bind
> >> maintainers or ISC?
> >>
> >>
> >>
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 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 ve
On Tue, Jan 14, 2025 at 10:47:35PM +0100, Emmanuel Fusté wrote:
! localhost is defined as a (local) hostname of the loopback interface, not a
! domain name.
Where would that be defined? Because, what You state is a
contradiction in itself: a hostname is a designation of the metal
(or virtual, now
On Wed, Jan 15, 2025 at 11:55 AM Ondřej Surý wrote:
>
> On 14. 1. 2025, at 16:56, Lee 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
Le 15/01/2025 à 17:12, Lee a écrit :
On Wed, Jan 15, 2025 at 5:41 AM Emmanuel Fusté wrote:
Le 15/01/2025 à 05:59, Nick Tait via bind-users a écrit :
On 15/01/2025 10:47, Emmanuel Fusté wrote:
If so, does the ISC ship a db.local with a wildcard - eg.
--- cut here ---
@ IN NS
> On 14. 1. 2025, at 16:56, Lee 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 c
On Wed, Jan 15, 2025 at 5:41 AM Emmanuel Fusté wrote:
>
> Le 15/01/2025 à 05:59, Nick Tait via bind-users a écrit :
> > On 15/01/2025 10:47, Emmanuel Fusté wrote:
> >>> If so, does the ISC ship a db.local with a wildcard - eg.
> >>>--- cut here ---
> >>> @ IN NS localhost.
> >>>
Le 15/01/2025 à 05:59, Nick Tait via bind-users a écrit :
On 15/01/2025 10:47, Emmanuel Fusté wrote:
If so, does the ISC ship a db.local with a wildcard - eg.
--- cut here ---
@ IN NS localhost.
@ IN A 127.0.0.1
@ IN ::1
* IN A
On 15/01/2025 10:47, Emmanuel Fusté wrote:
If so, does the ISC ship a db.local with a wildcard - eg.
--- cut here ---
@ IN NS localhost.
@ IN A 127.0.0.1
@ IN ::1
* IN A 127.0.0.1
IN ::1
--- cut here
Le 14/01/2025 à 16:56, Lee a écrit :
On Tue, Jan 14, 2025 at 9:06 AM Petr Špaček wrote:
It does not serve 'legitimate' purpose by itself, it just lowers cost of
leaked nonsense queries.
I guess it applies to most (all?) special-use names: The local
authoritative zone is to defined to cu
On 15/01/2025 4:56 am, Lee wrote:
Should bind answer when asked for an A record for random.name.localhost?
If so, does the ISC ship a db.local with a wildcard - eg.
--- cut here ---
@ IN NS localhost.
@ IN A 127.0.0.1
@ IN ::1
* IN
ry 14, 2025 10:48 AM
To: Robert Wagner
Cc: bind-users@lists.isc.org
Subject: Re: localhost name lookup
This email originated from outside of TESLA
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Tue, Jan 14, 2025 at 6:56 AM Robert Wagner
On Tue, Jan 14, 2025 at 9:06 AM Petr Špaček wrote:
>
> On 14. 01. 25 12:56, Robert Wagner wrote:
> > I wanted to better understand the use-case of having a DNS server
> > provide localhost lookup.
>
> TL;DR Mistakes are being made.
>
> It does not serve 'legitimate' purpose by itself, it just lower
case. I first had to install
= systemd-resolved and point DNS to 127.0.0.53 instead of using the
= locally installed bind on 127.0.0.1.
Thanks
Lee
>
> From: bind-users on behalf of Eric
>
> Sent: Sunday, January 12, 2025 9:39 PM
> To: Lee
> Cc
On Sun, Jan 12, 2025 at 9:39 PM Eric wrote:
>
> I did, but my thought would be it's up to the dns admin to define those zone
> configurations as you have done. I may be wrong though.
I may be wrong also - which is why I'm asking :)
There seems to be a long list of things bind tries to serve loca
On 14. 01. 25 12:56, Robert Wagner wrote:
I wanted to better understand the use-case of having a DNS server
provide localhost lookup.
TL;DR Mistakes are being made.
It does not serve 'legitimate' purpose by itself, it just lowers cost of
leaked nonsense queries.
I guess it applies to most (
anuary 12, 2025 9:39 PM
> *To:* Lee
> *Cc:* bind-users@lists.isc.org
> *Subject:* Re: localhost name lookup
>
> This email originated from outside of TESLA
>
> Do not click links or open attachments unless you recognize the sender and
> know the content is safe.
>
> I did,
something prevent you from reaching the DNS server (or network delays) - thus
improving uptime.
From: bind-users on behalf of Eric
Sent: Sunday, January 12, 2025 9:39 PM
To: Lee
Cc: bind-users@lists.isc.org
Subject: Re: localhost name lookup
This email
I did, but my thought would be it's up to the dns admin to define those zone
configurations as you have done. I may be wrong though.
Jan 12, 2025 6:36:03 PM Lee :
> On Sun, Jan 12, 2025 at 5:15 PM Eric wrote:
>>
>> That is means that the 'domain' is reserved and can be used locally. It
>> do
On Sun, Jan 12, 2025 at 5:15 PM Eric wrote:
>
> That is means that the 'domain' is reserved and can be used locally. It
> doesn't specify all records in that namespace / domain will resolve to
> 127.0.01.
>
> Think of it like .com
>
> If you want every A record in *.localhost to resolve to 127.0.
That is means that the 'domain' is reserved and can be used locally. It doesn't
specify all records in that namespace / domain will resolve to 127.0.01.
Think of it like .com
If you want every A record in *.localhost to resolve to 127.0.0.1 what you did
will do that.
Jan 12, 2025 4:38:09 PM Le
Excuse my ignorance, but
https://datatracker.ietf.org/doc/html/rfc6761#section-6.3
The domain "localhost." and any names falling within ".localhost."
are special in the following ways:
sure seems to mean that if I lookup curlmachine.localhost I should get
a 127.0.0.1 or ::1 address returne
29 matches
Mail list logo
