If you wish to decline the post, change the 'apppost' below to 'delpost'.
If you wish to edit the post, change it to 'modpost' and edit the message
as needed - not all mail programs will work with modpost.

--On 15 October 2004 12:38 -0700 "Hallam-Baker, Phillip" wrote:
> * The current wildcard, if www.example.com exists the
> wildcard *.example.com will NOT match for ANY record.
>
> *? The wildcard people think they have and mostly want,
> TXT/*.example.com will match iff www.example.com exists
> but has no other TXT record.
>
> As a matter of history quite a few DNS servers have actually
> implemented the nonstandard *? wildcard which is one reason
> for the confusion.
>
> The use cases given in the MARID case did not work, in particular
> is was not possible to construct a wildcard to say 'this machine
> does not send mail' since *.example.com will not match
> phill.example.com if there is ANY record for the node. The
> use case is real but it cannot be met without *? style wildcards.

Does the latter (*?) actually need any protocol-level specification?

By which I mean is it not possible to
a) On a strictly conformant server, emulate *? with a macro (or similar),
so
*? IN TXT foo
a IN TXT bar
b IN MX baz
becomes
* IN TXT foo
a IN TXT bar
b IN MX baz
b IN MX bar
b) If one wants to implement a server where * means "the other thing",
i.e. *? (and you note some servers have done this), say "* in a zone
file means *?" (and preferably provide a way to get *).

Alex

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive:
// eompost 41702FD5:B437.1bzccebgbpbyfqaffgq