Re: wildcard domain serving

2010/4/12 Matthew Dempsky <[email protected]>:
> 2010/4/12 Colm MacCárthaigh <[email protected]>:
>> Isn't there a risk that this data could make its way into additional
>> sections you serve?
>
> No, tinydns never includes wildcard records in the additional record section.

These relevant records provided in the e-mail are not wildcard records;

Z$tld:a.ns.example.com.:hostmaster.example.com
&$tld::a.ns.example.com:86400
&$tld::b.ns.example.com:86400

So if a.ns.example.com and b.ns.example.com have A records defined, it
seems like they would be included. I guess it depends on whether those
records are real, or simply defined by the wildcard.

>> E.g. if a "legitimate" domain you host has a CNAME, MX, SRV .. etc, to
>> something in com, net, org, then won't tinydns include glue claiming
>> a.ns.example.com , b.ns.example.com as the authority for .com, .net.
>> .org ? (if you do not also host the subdomain to which the
>> CNAME/whatever points).
>
> Even if it did, caches will discard those records as out-of-bailiwick poison.

They may also discard the entire response as authoritative and cacheable :/

-- 
Colm