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
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
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
>
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
> 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 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