On 01/04/16 11:52, Niall O'Reilly wrote:
If you are going to pick a single authority for a particular label, it
should be the zone that determines whether that label exists or not.
That seems no less arbitrary a rule of thumb than one which would
give priority to the zone which contains
On 1 Apr 2016, at 11:08, Tony Finch wrote:
> Robert Edmonds wrote:
>> Tony Finch wrote:
>>> Phil Mayers wrote:
What is considered the source of the ownername for, say, "com."?
>>>
>>> It should be the root zone master file.
>>
>> Why not the com zone master file?
>
> If you are going
Robert Edmonds wrote:
> Tony Finch wrote:
> > Phil Mayers wrote:
> > >
> > > What is considered the source of the ownername for, say, "com."?
> >
> > It should be the root zone master file.
>
> Why not the com zone master file?
If you are going to pick a single authority for a particular label,
gt; To: Mike Bernhardt
> Cc: bind-us...@isc.org
> Subject: Re: BIND started replying to queries for .com with .COM
>
>
> Your monitoring probe is broken.
>
> STD 13 says that that the DNS is case preserving. The problem is that lots
> of servers aren't case p
Tony Finch wrote:
> Phil Mayers wrote:
> >
> > What is considered the source of the ownername for, say, "com."?
>
> It should be the root zone master file.
Why not the com zone master file?
--
Robert Edmonds
___
Please visit https://lists.isc.org/mai
ailto:ma...@isc.org]
Sent: Tuesday, March 29, 2016 5:19 PM
To: Mike Bernhardt
Cc: bind-us...@isc.org
Subject: Re: BIND started replying to queries for .com with .COM
Your monitoring probe is broken.
STD 13 says that that the DNS is case preserving. The problem is that lots
of servers aren't ca
On 30/03/2016 13:15, Tony Finch wrote:
Phil Mayers wrote:
On 30/03/16 10:50, Tony Finch wrote:
Yes, we encountered that problem recently :-) You can revert to the old
behaviour using
no-case-compress { any; };
+1 super confusing when we first ran into it (Exim dnslookup.c, by any c
On 30/03/2016 13:32, Mark Andrews wrote:
That said anything matching ownernames should be doing this case
insensitively.
Absolutely. In our case it was something a little more subtle - the app
(Exim) was actually looking for case-changed replies and altering its
input to match, which under c
On 30/03/2016 13:23, Tony Finch wrote:
Phil Mayers wrote:
What is considered the source of the ownername for, say, "com."?
It should be the root zone master file.
Doh, of course - brainfade, it should be the root.
I am mildly surprised that the root and TLD/2LD servers aren't doing the
r
In message <56fbbe83.6080...@imperial.ac.uk>, Phil Mayers writes:
> On 30/03/2016 12:25, Mark Andrews wrote:
>
> > The recent change was to record and return the learnt case of
> > ownernames (to the RRset level) rather than use whatever was used
> > to build the red-black tree names.
>
> What i
Phil Mayers wrote:
>
> What is considered the source of the ownername for, say, "com."?
It should be the root zone master file.
However authoritative server implementations differ in whether they echo
the query case or preserve the master case. e.g. a.root-servers.net
(running Verisign ATLAS) ec
Phil Mayers wrote:
> On 30/03/16 10:50, Tony Finch wrote:
> >
> > Yes, we encountered that problem recently :-) You can revert to the old
> > behaviour using
> >
> > no-case-compress { any; };
>
> +1 super confusing when we first ran into it (Exim dnslookup.c, by any
> chance? ;o)
Actually N
On 30/03/2016 12:25, Mark Andrews wrote:
The recent change was to record and return the learnt case of
ownernames (to the RRset level) rather than use whatever was used
to build the red-black tree names.
What is considered the source of the ownername for, say, "com."? One
thing I saw when I w
In message <56fbb385.5070...@imperial.ac.uk>, Phil Mayers writes:
> On 30/03/16 01:19, Mark Andrews wrote:
> >
> > Your monitoring probe is broken.
> >
> > STD 13 says that that the DNS is case preserving. The problem is
> > that lots of servers aren't case preserving instead they echo back
> > t
On 30/03/16 01:19, Mark Andrews wrote:
Your monitoring probe is broken.
STD 13 says that that the DNS is case preserving. The problem is
that lots of servers aren't case preserving instead they echo back
the query case in the owner names of records returned which named
then records.
Can I be
On 30/03/16 10:50, Tony Finch wrote:
Yes, we encountered that problem recently :-) You can revert to the old
behaviour using
no-case-compress { any; };
+1 super confusing when we first ran into it (Exim dnslookup.c, by any
chance? ;o)
In detail, since I spent ages figuring this ou
Mike Bernhardt wrote:
> I rebooted one of our BIND VMs this morning. It's running BIND 9.10.3-P3. We
> noticed that queries for domains with domain.com were answered with
> domain.COM with the .COM in capital letters. Other high-levels like .org
> were not changed. It caused a monitoring probe to
Your monitoring probe is broken.
STD 13 says that that the DNS is case preserving. The problem is
that lots of servers aren't case preserving instead they echo back
the query case in the owner names of records returned which named
then records.
In message <030101d18a06$fa21c8d0$ee655a70$@bart.g
18 matches
Mail list logo
