Thank you very much, makes perfect sense. Can we increase the timeout
somehow or specify it as a tunable query parameter? I find the OARC tester
highly useful in conjunction with RIPE ATLAS.
On Dec 26, 2015 12:24 PM, "Anand Buddhdev" wrote:
> On 24/12/15 10:59, Gil Bahat wrote:
>
> Dear Gil,
>
>
On 24/12/15 10:59, Gil Bahat wrote:
Dear Gil,
> Unfortunately, this doesn't seem to work so well either:
> https://atlas.ripe.net/measurements/3115499/
> Can anyone here help me figure out why almost all requests end up being
> null and only very few of them show up the resultant TXT record?
The
Unfortunately, this doesn't seem to work so well either:
https://atlas.ripe.net/measurements/3115499/
Can anyone here help me figure out why almost all requests end up being
null and only very few of them show up the resultant TXT record?
Gil
On Thu, Dec 24, 2015 at 11:44 AM, Gil Bahat wrote:
>
actually, It would be extremely useful for the DNS probe results to
immediately and clearly reflect whether any response included EDNS0 bits or
not, without this being a separate test. I am trying to debug some oddball
CDN DNS assignments and this means trying to hunt down specific probes and
tweak
On Wed, Dec 09, 2015 at 08:51:21PM +0200,
Micha Bailey wrote
a message of 48 lines which said:
> > A partial workaround is to use ANY as a query_type.
> >
> > Not necessarily:
> https://tools.ietf.org/html/draft-jabley-dnsop-refuse-any-00#section-8 and
> http://blog.cloudflare.com/deprecating-
On Wed, Dec 09, 2015 at 02:53:42PM -0500,
Jared Mauch wrote
a message of 20 lines which said:
> Perhaps a method to just set the RRType as integer would work in the
> interim?
+1 for me.
On Thu 2015-12-10 07:41:29 -0500, Philip Homburg wrote:
> On 2015/12/10 13:33 , Jared Mauch wrote:
>> client-subnet? :)
>
> I can add an option to send 0/0 as the client subnet :-)
That would be great, thanks!
--dkg
On 2015/12/10 13:43 , Gil Bahat wrote:
> what could be very interesting though, is to map DNS servers supporting
> EDNS0 and ones not supporting it (i.e. which network operators should be
> bugged to support it...). it would be very good for network operators to
> see e.g. in-country adoption rate
On Thu, Dec 10, 2015 at 2:33 PM, Jared Mauch wrote:
>
> > On Dec 10, 2015, at 6:21 AM, Philip Homburg
> wrote:
> >
> > On 2015/12/10 10:11 , Willem Toorop wrote:
> >> And sending arbitrary EDNS0 options? Have you ever considered that too?
> >> Is it on the todo list too?
> >
> > Hi Willem,
> >
On 2015/12/10 13:33 , Jared Mauch wrote:
> client-subnet? :)
I can add an option to send 0/0 as the client subnet :-)
> On Dec 10, 2015, at 6:21 AM, Philip Homburg wrote:
>
> On 2015/12/10 10:11 , Willem Toorop wrote:
>> And sending arbitrary EDNS0 options? Have you ever considered that too?
>> Is it on the todo list too?
>
> Hi Willem,
>
> Just about all EDNS0 options take parameters. It is not part of the
On 2015/12/10 10:11 , Willem Toorop wrote:
> And sending arbitrary EDNS0 options? Have you ever considered that too?
> Is it on the todo list too?
Hi Willem,
Just about all EDNS0 options take parameters. It is not part of the
model to allow users to inject arbitrary binary data. Though if there
Op 09-12-15 om 21:58 schreef Robert Kisteleki:
> We plan to have a whitelist [of query IDs], both because the probes just
> don't fully support all types, and some users expressed that they would not
> like us to support all query types; for example axfr/ixfr are complicated
> examples.
And sendin
Op 09-12-15 om 17:01 schreef Stephane Bortzmeyer:
> On Wed, Dec 09, 2015 at 10:49:09AM -0500,
> Shumon Huque wrote
> a message of 26 lines which said:
>> Is this feasible? Are others interested in this capability?
>
> Count me in.
Me too!
-- Willem
On 2015-12-09 20:53, Jared Mauch wrote:
>
>> On Dec 9, 2015, at 2:39 PM, Randy Bush wrote:
>>
>>> I'd like to request the ability to have RIPE Atlas probes be able to issue
>>> DNS queries for arbitrary record types, and have that capability exposed in
>>> the API. I'm particularly interested in
> On Dec 9, 2015, at 2:39 PM, Randy Bush wrote:
>
>> I'd like to request the ability to have RIPE Atlas probes be able to issue
>> DNS queries for arbitrary record types, and have that capability exposed in
>> the API. I'm particularly interested in newer DANE record types like TLSA,
>> OPENPGPK
> I'd like to request the ability to have RIPE Atlas probes be able to issue
> DNS queries for arbitrary record types, and have that capability exposed in
> the API. I'm particularly interested in newer DANE record types like TLSA,
> OPENPGPKEY, SMIMEA, etc but a general purpose mechanism would be
On Wednesday, December 9, 2015, Stephane Bortzmeyer
wrote:
> On Wed, Dec 09, 2015 at 10:49:09AM -0500,
> Shumon Huque > wrote
> a message of 26 lines which said:
>
>
> > I'm particularly interested in newer DANE reacord types like TLSA,
> > OPENPGPKEY, SMIMEA, etc but a general purpose mechanis
On Wed, Dec 09, 2015 at 10:49:09AM -0500,
Shumon Huque wrote
a message of 26 lines which said:
> I'd like to request the ability to have RIPE Atlas probes be able to issue
> DNS queries for arbitrary record types, and have that capability exposed in
> the API.
By the way, this (real) limit do
I'd like to request the ability to have RIPE Atlas probes be able to issue
DNS queries for arbitrary record types, and have that capability exposed in
the API. I'm particularly interested in newer DANE record types like TLSA,
OPENPGPKEY, SMIMEA, etc but a general purpose mechanism would be useful.
20 matches
Mail list logo
