On 02/03/2024 11:36, Greg Choules wrote:
Please don't encourage using "search" in resolv.conf or the Windows
equivalent. Search domains make queries take longer, impose
unnecessary load on resolvers and make diagnosis of issues harder
because, when users say "it doesn't work" you have no idea
Please don't encourage using "search" in resolv.conf or the Windows
equivalent. Search domains make queries take longer, impose unnecessary
load on resolvers and make diagnosis of issues harder because, when users
say "it doesn't work" you have no idea what it was that didn't work.
I tried using
On 02/03/2024 03:42, Mike Mitchell via bind-users wrote:
Our networking team is in the habit of entering the IP address of every
network interface on a router under one name. The very first address
entry is their out-of-band management interface. "rrset-order fixed" is
used on their domain
Hi there,
On Fri, 1 Mar 2024, Petr ?pa?ek wrote:
On 01. 03. 24 12:23, G.W. Haywood wrote:
... Maybe the lesson here is that if you're using BIND other than
because it happened to come with your distro, then it's probably a
good idea to keep an eye on this list to monitor the plans for
On Fri, 1 Mar 2024, Ondřej Surý wrote:
I wanted to address this comment. We (the developers) don't remove the
features out of convenience or because we have 'better idea'.
It's a known problem with humans that the discipline to remove items is
oftentimes lacking, and that humans will tend to
Our networking team is in the habit of entering the IP address of every network
interface on a router under one name. The very first address entry is their
out-of-band management interface. "rrset-order fixed" is used on their domain
for address records, so they can ssh to the router by name
On 01. 03. 24 12:23, G.W. Haywood wrote:
Do you have reasons for keeping 'inline-signing' or 'auto-dnssec'
configurations? Is there a use case that is not (yet) covered by
'dnssec-policy'? Any other concerns? Please let us know.
On 01/03/2024 11:02, Jim Reid wrote:
On 1 Mar 2024, at 10:37, Greg Choules via bind-users
wrote:
In summary, Do the hard work of traffic steering somewhere else and let your
DNS resolvers deliver the chosen answer. Don't make the resolvers themselves
try to do this on the basis of
On 29 Feb 2024, at 21:39, Ondřej Surý wrote:
> Hey,
>
> BIND 9 supports a fixed rrset ordering (that is keeping the order of the
> RRSets from the zone file). It has to be configured
> at the compile time, it takes more memory (to record that order) and it's a
> #ifdef all over the places.
>
Hi there,
On Fri, 1 Mar 2024, Ond?ej Sur? wrote:
On 26. 2. 2024, at 22:41, Al Whaley wrote:
> A lot of pain and suffering in this world comes from people being
> sure they have a 'better idea' and everybody needs to do whatever.
> This feels a bit like that. ...
... ultimately, the developers
> On 1 Mar 2024, at 10:37, Greg Choules via bind-users
> wrote:
>
> In summary, Do the hard work of traffic steering somewhere else and let your
> DNS resolvers deliver the chosen answer. Don't make the resolvers themselves
> try to do this on the basis of incomplete information.
Well said
This is usually a symptom of child NS being broken. It works with empty cache
because of the NS records in parent work, but then child NS take over and boom!
--
Ondřej Surý — ISC (He/Him)
My working hours and your working hours may be different. Please do not feel
obligated to reply outside
On 29.02.24 15:20, Ludovit Koren wrote:
occasionally I get the following SERVFAIL error:
dig www.jiscd.sk
; <<>> DiG 9.18.24 <<>> www.jiscd.sk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 12207
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY:
2nd $beverage consumed.
I have never liked sortlist since I inherited it 16 years ago in my
previous job.
For me it suffers from at least one fundamental problem:
- If a client, say at location "1", is given a bunch of sorted A records
with the server at location "1" first, what does the client
Hi there,
On Fri, 1 Mar 2024, Matus UHLAR wrote:
On 01.03.24 08:24, Ond?ej Sur? wrote:
> The "sortlist" option allows to define a complicated rules when and
> how to reorder the resource records in the responses. The same
> caveats as with the "rrset-order" apply - relying on any specific
>
On 01.03.24 08:24, Ondřej Surý wrote:
The "sortlist" option allows to define a complicated rules when and
how to reorder the resource records in the responses. The same
caveats as with the "rrset-order" apply - relying on any specific
order of resource records in the DNS responses is wrong.
We
On 01. 03. 24 8:01, Ondřej Surý wrote:
On 26. 2. 2024, at 22:41, Al Whaley wrote:
A lot of pain and suffering in this world comes from people being sure they
have a 'better idea' and everybody needs to do whatever. This feels a bit like
that. A command that gives choice and real certainty
> Peter Davies writes:
> Hi Ludovit,
> It looks like you have two version of the jiscd.sk zone.
> host -C jiscd.sk
> Nameserver 2001:67c:1bd4:8080::20:
> jiscd.sk has SOA record ns1.gov.sk. gov.sk. 2024022501 7200 3600
> 604800 86400
> Nameserver
18 matches
Mail list logo
