On 13/01/2025 12:44, Lee wrote:
As long as I'm asking ignorant questions.. is there some reason why
bind (at least as it came configured on my Debian machine) looks up
.local names?
I added this bit to named.conf to do what seemed reasonable. But
again - it seems reasonable _to me_ I dunno if a
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
As long as I'm asking ignorant questions.. is there some reason why
bind (at least as it came configured on my Debian machine) looks up
.local names?
I added this bit to named.conf to do what seemed reasonable. But
again - it seems reasonable _to me_ I dunno if anyone else agrees & it
seems like
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
6 matches
Mail list logo
