On Mon, 15 Sep 2003, at 7:57pm, [EMAIL PROTECTED] wrote:
> As of a little while ago (it is around 7:45 PM US Eastern on Mon 15 Sep
> 2003 as I write this), VeriSign added a wildcard A record to the .COM and
> .NET TLD DNS zones. The IP address returned is <64.94.110.11>, which
> reverses to .
p
> Subject: RE: All .COM / .NET domain names now exist
>
>
> > This will have the immediate effect of making network trouble-shooting
> > much more difficult. Before, a mis-typed domain name in an
> email address,
> > web browser, or other network configuration
> This will have the immediate effect of making network trouble-shooting
> much more difficult. Before, a mis-typed domain name in an email address,
> web browser, or other network configuration item would result in
> an obvious
> error message. You might not have known what to do about it, but
On Mon, 15 Sep 2003, at 10:35pm, [EMAIL PROTECTED] wrote:
> ... but I can't verify this. Domains that don't exist are correctly
> returning NXDOMAIN on my systems, even after flushing the caches on my
> local nameservers.
>
> How did you determine this to be the case?
I was alerted to the prob
