[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [wg-c] Mark's Proposal
sigh. didn't get the automatic processing installed in time
The good news is that this shows why this topic cannot be discussed
independently of the technical issues.
*****
FOR ANYONE WHO DOES NOT FULLY UNDERSTAND THE
TECHNICAL REASON THAT SIMON'S EXERCISE DOES NOT
AT ALL DEMONSTRATE WHAT HE IS CLAIMING, PLEASE
FOLLOW THE REMAINING PEDAGOGY CAREFULLY.
*****
And Simon, I compliment you on using a moderately creative bit of
mis-direction.
One almost did not see the hand switch the entries and servers...
At 11:32 PM 4/10/00 -0700, Simon Higgs wrote:
[simon@vaio simon]$ nslookup 208.1.127.5 joy.songbird.com
> Server: joy.songbird.com
> Address: 208.184.79.7
>
> Name: berk.serv.nic.info
> Address: 208.1.127.5
Alas, I had not noticed that you were doing a REVERSE DNS lookup, rather
than a forward one.
Here we go with the detailed analysis:
STEP #1 (using dig rather than nslookup)
>[dcrocker]: dig -x 208.1.127.5
>
>; <<>> DiG 8.1 <<>> -x
>;; QUERY SECTION:
>;; 5.127.1.208.in-addr.arpa, type = ANY, class = IN
>
>;; ANSWER SECTION:
>5.127.1.208.in-addr.arpa. 1h59m3s IN PTR berk.serv.nic.info.
>
>;; AUTHORITY SECTION:
>127.1.208.in-addr.arpa. 1h59m3s IN NS lanshark.lanminds.com.
>127.1.208.in-addr.arpa. 1h59m3s IN NS lanfill.lanminds.com.
>127.1.208.in-addr.arpa. 1h59m3s IN NS bellpepper.lanminds.net.
>
>;; ADDITIONAL SECTION:
>lanshark.lanminds.com. 1d23h58m59s IN A 208.25.68.5
>lanfill.lanminds.com. 1d23h58m59s IN A 208.25.68.10
>bellpepper.lanminds.net. 11h52m20s IN A 207.174.24.16
This shows:
a) the lookup was a reverse lookup, through in-addr.arpa, not through
berk.serv.nic.info. That is, it does not show that berk.serv.nic.info will
resolve. The owner of the cited IP address, 5.127.1.208, may place any
little bit of name silliness they wish into their reverse DNS entry.
b) the entry is administered by folks at "lanminds.com".
We could stop, here, since that sufficiently shows that Simon's
demonstration did NOT show anything at all about the ability to resolve
.info. However...
STEP #2
lanminds.com is not part of CORE and is not listed by ICANN.
STEP #3
>[dcrocker]svpal: nslookup 208.1.127.5 lanshark.lanminds.com
>Server: lanshark.lanminds.com
>Address: 208.25.68.5
>
>Name: berk.serv.nic.info
The folks listing the reverse DNS entry DO resolve the .info-based name
correctly.
STEP #4
Compare lanminds' processing of .com and .info:
>[dcrocker]: nslookup info lanshark.lanminds.com
>Server: lanshark.lanminds.com
>Address: 208.25.68.5
>
>*** lanshark.lanminds.com can't find info: Non-existent host/domain
>[dcrocker]: nslookup .info lanshark.lanminds.com
>Server: lanshark.lanminds.com
>Address: 208.25.68.5
>
>*** lanshark.lanminds.com can't find .info: Unspecified error
>
>[dcrocker]: nslookup com lanshark.lanminds.com
>Server: lanshark.lanminds.com
>Address: 208.25.68.5
>
>Name: com
It finds com just fine but can't resolve info. Since it CAN resolve a full
.info-based name, that means that .info queries are being processed
specially, rather than through "the" root.
In other words, the fine folks at Lanminds are subscribing to some
non-IANA/non-ICANN service that supplies entries for .info.
And, therefore, Simon's supplied example does not demonstrate anything at
all about CORE or the IANA root.
d/
ps. What all this DOES demonstrate, quite effectively, is that time will
be used more effectively my rapid installation of the automatic processor
for mail from Simon.
=-=-=-=-=
Dave Crocker <dcrocker@brandenburg.com>
Brandenburg Consulting <www.brandenburg.com>
Tel: +1.408.246.8253, Fax: +1.408.273.6464
675 Spruce Drive, Sunnyvale, CA 94086 USA