Re: new bind

[Mike Ayers <mike.ayers@earthling.net>]

Peter H. Coffin wrote:

> Which kind of demonstgrates the futility of munging up examples that A)
> aren't OBVIOUSLY examples, and 

	I don't know that it was an example.  I took it to be a live internal 
domain behind a firewall.  I am thinking of a configuration like mine. 
You can resolve skunk.sytes.net (try it), but you cannot resolve 
frankenputer.skunk.sytes.net.  I can resolve both.  This is because my 
internal DNS server, which has no external interfaces, is authoritative 
for the domain within the domain, while the servers at no-ip.com are 
authoritative outside of the domain (astute observers will note that 
this implementation is contrary to the strict interpretation of DNS - it 
is a compromise intended to fit modern practice and problems).  It was 
my belief that the OP was setting up somethig similar, probably without 
setting up an authoritative domain externally.  As for whether or not a 
domain whose whois query does not resolve is not obviously an example, 
we apparently differ in opinion, but I agree that he could/should have 
included more information on what domain he did set up.

 > B) might otherwise reveal information
> that would point to a solution. "I run chobitsfan.org, and I can't
> resolve www.chobitsfan.org" will have vastly different solutions
> depending on whether someone else can resolve www.chobitsfan.org.

	True.  Also important is whether or not someone else *should* be able 
to resolve www.chobitsfan.org.  However, to me, it is more important to 
get the dig session.  This can tell me a lot that I would need to know, 
and I'd like to call the OP (still listening, Bryan?) on it, even though 
I don't need it anymore.  This is why I believed that justatest.org was 
a live internal setup - that way the DNS maps could be posted without 
compromise, since they would be invalidated as soon as all issues were 
resolved.


/|/|ike