Re: [gnso-dow123] Question 2 on tomorrow's call

[Bret Fausett <bfausett@xxxxxxxxxxxxxxxx>]

On Steve's point, I have always understood the admin and technical 
points of contact in the whois domain name database as persons to 
contact for DNS-related issues. For example, I registered "blog.us" and 
provide DNS for third-level domains to friends and others who want a 
name. Marty Schwimmer has http://trademark.blog.us, but I have no 
control over the content on his web site. If the DNS info were 
misconfigured, however, Marty, or someone else, could contact me through 
the blog.us contact information to correct it. I suppose I could delete 
Marty's DNS information, but that would only delete the pointer, not the 
content itself (which could still be accessed via Marty's other domain 
name pointing to the same host, http://www.schwimmerlegal.com, or 
perhaps by IP address directly, depending on how Apache were configured).

For content issues, as opposed to DNS issues, I would locate the IP 
address of the host computer and then use ARIN's whois to find out what 
company was hosting the site. That's the company I would expect to 
respond to me about content issues.

        Bret