[Dnsmasq-discuss] Handling unknown RTYPEs and querying for version...

[Nicholas Weaver]

Thanks!  Yeah, the ID is very useful (we can use that to get
information from specific sessions)


Unfortunately I don't know how to coerce dig into using unknown query
types (its a custom written DNS library in Java that we use, RTYPE=169
is the rtype # we use, and the data format is that of a txt record).

The server identification makes sense, because what it does is it
queries for a special name (server.netalyzr.icsi.berkeley.edu) which
returns the IP address where the request eventually came from, so the
path was

Applet -> NAT -> (ISP) -> Authority.

Which is the IP which the server's requset comes from (often these ISP
dns servers are clutery-beasts which will issue the outbound request
through).

Although F-me, the transcript looks like it passed, but the display
doesn't, so I think this may be a rendering bug?!?

On Mon, Nov 29, 2010 at 12:57 PM, Simon Kelley <simon at thekelleys.org.uk> wrote:
> On 29/11/10 19:30, Nicholas Weaver wrote:
>
>> RFC3597 specifically states how they should be handled (as opaque
>> binary data which is passed unchanged), but almost all fail to process
>> our request for a made-up type (type # 169).
>>
>> a)  Could someone run Netalyzr against a NAT running the latest
>> Dnsmasq code and send me the result link?
>
> OK, I just did this, and got the error.
>
> Your NAT has a built-in DNS proxy. We sent it a DNS request and our server
> received it from 62.253.128.100.
> Some or all specialized DNS types checked are not properly interpreted by
> the NAT's DNS proxy. The following tested queries were blocked/failed:
>
>    * RTYPE=169 (deliberately unknown) records.
>
>
> 62.253.128.100 is cmbg-dnsany-1.server.virginmedia.net. which makes sense,
> as my ISP is viginmedia. I'm very sure that a query for RTYPE=169 will have
> been forwarded Ok by dnsmasq, so  maybe the problem is at the ISP end?
>
> Is there a command line tool that will generate these queries simply? dig
> only sends queries whose name it knows.
>
> The ID of the netalyzer run was  43ca208a-28815-3a04eee7-dbda-4220-84b4 if
> that's useful.
>
>
> Cheers,
>
> Simon.
>
>
>