[62898] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: Detecting a non-existent domain

daemon@ATHENA.MIT.EDU (Kee Hinckley)
Tue Sep 23 20:17:13 2003

In-Reply-To: <MDEHLPKNGKAHNMBLJOLKEEJMGNAA.davids@webmaster.com>
Date: Tue, 23 Sep 2003 20:16:04 -0400
To: "David Schwartz" <davids@webmaster.com>
From: Kee Hinckley <nazgul@somewhere.com>
Cc: <nanog@merit.edu>
Errors-To: owner-nanog-outgoing@merit.edu


At 3:15 PM -0700 9/23/03, David Schwartz wrote:
>	How would you do this before? Does an A record for a hostname 
>mean that a
>host with that name exists? If so, then all *.com 'hosts' now 'exist'. If
>not, what did you mean by exist before?

Okay, let's be very specific.  I need to know if a given name has 
either A or MX records which are *not* the same as those provided by 
the a wildcard in the appropriate TLD.

The answer so far seems to be to query *.TLD, nab all the records, 
and then compare them all the results you get back from querying the 
domain.  If there is anything that doesn't match, you are in the 
clear.  (Modulo internal networks and localhost and all those fun 
tricks of course--but that's a different problem.)

The fact that this is a single IP comparison with Verisign today 
presumably does not preclude the wonders of MX records, CNAME's, 
multiple A records and all of that in the future.
-- 
Kee Hinckley
http://www.messagefire.com/         Next Generation Spam Defense
http://commons.somewhere.com/buzz/  Writings on Technology and Society

I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.

home help back first fref pref prev next nref lref last post