Hi Ondrey and others!
I have tested 9.20.4-3+ubuntu24.04.1+deb.sury.org+1 on one of our RcodeZero
production nodes for 1 week and have not encountered any timeouts anymore.
XFR speed also seems fine now.
Regards
Klaus
From: Ondřej Surý
Sent: Thursday, December 5, 2024 8:36 PM
To: Klaus Darili
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
On 15/01/2025 6:09 am, Lee wrote:
I don't have a whole lot of options there. The clients are a mixture
of Windows and Apple products.. about all I can do (or at least all I
know how to do) is use DHCP to give them a domain name and point them
to a resolver.
My understanding is:
* Apple device
IMO nothing.
If a client really wanted a meaningful answer for a .local name, it
wouldn't be asking your resolver the question; it would be making a
multicast-DNS query.
--
Do things because you should, not just because you can.
John Thurston907-465-8591
john.thurs...@alaska.gov
Departme
On Mon, Jan 13, 2025 at 2:54 AM Nick Tait via bind-users wrote:
>
> 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.con
Looking at a Rocky9 box...
ping localhost
ping squirrel.localhost
ping curl.localhost
all resolve to 127.0.0.1. Avg response .043-.047ms for each. Pinging another
ip is like 10-20 times slower.
The localhosts file contains:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.loc
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
On Tue, Jan 14, 2025 at 6:56 AM Robert Wagner wrote:
>
> All,
> I wanted to better understand the use-case of having a DNS server provide
> localhost lookup. I think every OS has a hosts file with localhost set for
> 127.0.0.1. This is an instantaneous resolution for localhost, rather than
> goi
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 (
Hi Robert.
Having localhost in /etc/hosts works if both of these conditions are
satisfied, I think:
1) The client asking the question is on the same box.
2) /etc/nsswitch.conf has been configured to look in hosts first, DNS second
If the client is local but nsswitch says to do DNS first then names
All,
I wanted to better understand the use-case of having a DNS server provide
localhost lookup. I think every OS has a hosts file with localhost set for
127.0.0.1. This is an instantaneous resolution for localhost, rather than going
through the process of setting of a network connection or wors
14 matches
Mail list logo
