Re: Send-N draft: draft-bellis-enum-send-n-02 published

On Jul 1, 2008, at 12:19 AM, Duane wrote:

> Clive D.W. Feather wrote:
>
>> The same happens if you put an A record at a higher level. So don't  
>> do that.
>
> Only if you request ANY/ALL, if you specifically request NAPTR it
> shouldn't, which is why someone else suggested you make a new DNS type
> to store send-n against then naptr wouldn't break except for the case
> where someone requested ANY/ALL

Regardless of the type at the higher name, simply the existence of a  
name will cause wildcards not to expand for that name.

As an example using the following records:

bob.harry.example TXT   test
*.example           NAPTR [whatever]

Will cause the following queries NOT to result in a wildcard expansion:

example NAPTR
harry.example NAPTR
bob.harry.example NAPTR
john.bob.harry.example NAPTR

All these will lead to NODATA errors (RCODE=0 plus empty answer section)

Regards,

Roy