Original sentence: In the examples listed above, the query for  for an MX record would match a wild card despite the domain  existing.In the examples listed above, the query for  for an MX record would match, despite  explicitly existing with only an A record.Microsoft's DNS server (if configured to do so) and MaraDNS (by default) have wildcards also match all requests for empty resource record sets, i.Some of the variations include:.To quote from RFC 4592, many DNS implementations diverge, in different ways, from the original definition of wildcards
Edited sentence: All DNS servers implement wildcards differently, both from RFC 1034 and from one another.If configured to do so, both Microsoft's DNS server and MaraDNS (by default) have wildcards also match all requests for empty resource record sets, i.In other words, if there is an MX record for "*.No DNS server software implements wildcards as per RFC 1034.This has the behaviour in conjunction with MX records that, in the main, people actually desire.This is in part because, as defined in RFC 1034, wildcard behaviour is not what people generally expect, particularly the interactions between wildcards and MX records.Whilst the aforegiven definition is in accordance with RFC 1034 § 4.3.2, it is not actually the case in practice.com" is "that doesn't exist"; the actual response with Microsoft's DNS server and MaraDNS is the MX record attached to "*.com", and an A record (but no MX record) for "www.com", the "correct" response to an MX request for "www