Quoting Kirk Fletcher on Sunday December 03, 2006:
| 
| I think they misunderstood the ICANN article, which refers to wildcard
| records in TOP LEVEL DOMAINS - ie, it makes a case against
| registries using wildcards for non existant or unregistered domains....
| what individuals do with their own domains is not any of their business
| - indeed, many services rely on a wildcard DNS entry for subdomains.
|
| auDA's statement, "auDA notes that the use of wildcard resource
| records is widely regarded within the internet technology community
| as detrimental to the operational stability of the DNS," is simply not
| correct in this context.  Again, I think they misunderstood the ICANN
| report as referring to use of wildcards in all levels (ie, subdomains).
| 
| Of course, it seems they are referring specifically to TLD.com.au
| domains (eg, com.com.au), but I think they need to make it a bit
| clearer - as it stands, the final sentence is disturbing:
| 
| "In the meantime, registrants who use wildcard resource records
| should be aware that auDA will take action to protect the operational
| stability and utility of the .au DNS."

There are technical issues associated with having wildcards like
"*.de.com.au" that would affect the correct operation of ".de" domains.
For example, one ccTLD registry reports getting 14,000 misdirected
queries a minute due to this problem.

I don't know if this is what auDA is targetting, but it is not correct
to say wildcards only impact at the second level (which I assume you
mean, as opposed to a wildcard at the top level would be "*.")

There is currently an ICANN RSTEP process evaluating this specific
technical issue and will deliver its report in the next few days.

kim