<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face="Courier New" size=2><SPAN class=786194301-12052003>On this
note, I think it would be nice if we had (at least) dual forward
resolves:</SPAN></FONT></DIV>
<DIV><FONT face="Courier New" size=2><SPAN
class=786194301-12052003></SPAN></FONT> </DIV>
<DIV><FONT face="Courier New" size=2><SPAN
class=786194301-12052003>fdf.wan.melbourne.wireless.org.au +
<DIV><FONT face="Courier New" size=2><SPAN
class=786194301-12052003>fdf.south-melb.wan.melbourne.wireless.org.au
</SPAN></FONT></DIV>
<DIV><FONT face="Courier New" size=2><SPAN
class=786194301-12052003></SPAN></FONT> </DIV>
<DIV><FONT face="Courier New" size=2><SPAN class=786194301-12052003>But have our
reverse resolution be verbose (eg: the full location). This would make
traceroutes more meaningful (not to mention really cool!)</SPAN></FONT></DIV>
<DIV><FONT face="Courier New" size=2><SPAN
class=786194301-12052003></SPAN></FONT> </DIV>
<DIV><FONT face="Courier New" size=2><SPAN
class=786194301-12052003>
Fenn.</SPAN></FONT></DIV></SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
owner-melbwireless@wireless.org.au [mailto:owner-melbwireless@wireless.org.au]
<B>On Behalf Of </B>Matt<BR><B>Sent:</B> Monday, 12 May 2003 11:27
AM<BR><B>To:</B> Melbourne Wireless; Routing Workgroup<BR><B>Subject:</B> Re:
[MLB-WIRELESS] Melbwirelses DNS and Domain Names<BR><BR></FONT></DIV>But isn't
the point of DNS that you don't need to remember ip addresses or associate a
url with a location? If someones looking for a resource on the network does it
really matter where it is? you just need to know if you've got connectivity
and what the ip address is. <BR><BR>An access point isn't likely to be running
anything worthwhile, probably just routing a bit of data maybe a webserver.
The interesting stuff will be hanging off that, the clients who are running
game servers, the ptp stuff that might have los to a couple of aps and be
sending traffic through both.<BR><BR>Once the network is built and theres a
degree more connectivity, then the people who need to know or who want to can
simply look up in the node database node bcg and see that I'm running a
webserver at something like bcg.wireless.org.au. Using global urls might make
it easier to run a dns that sits on both the internet and the wireless
networks so people can specify one dns and not have to split searching for
internet and other domains off on different servers (which might be difficult
to do??). All you need to know about me is that my node name is bcg, not that
I'm in the innernorth and I'm running an AP near an oef.<BR><BR>2c
more<BR>Matt<BR><BR><BR><BR>At 10:52 AM 12/5/2003 +1000, Matthew Hill
wrote:<BR>
<BLOCKQUOTE class=cite cite="" type="cite"><FONT face=verdana size=2>Ryan
and all</FONT><BR> <BR><FONT face=verdana size=2>This is what i wanted
to bring up a while ago and they werent
interested.</FONT><BR> <BR><FONT face=verdana size=2>This is similar to
what perth suggests, and what your suggested in your example, rocks. Exactly
what is possbily should be. </FONT><BR> <BR><A
href="http://www.wantirna-ap1.oef.mw">www.wantirna-ap1.oef.mw</A><FONT
face=verdana size=2> says exsactly where it is, </FONT><BR> <BR><FONT
face=verdana size=2><A
href="http://www.thebigfella.peninsula.mw">www.thebigfella.peninsula.mw</A>
that would be mine ...</FONT><BR> <BR><FONT face=verdana
size=2>Al;though i can see it being a while since we dont have alot of
the areas connected, it doesnt hurrt to have something implemented early so
it fits in oncec connected.</FONT><BR> <BR><FONT face=verdana
size=2>Cheers</FONT><BR> <BR><FONT face=verdana size=2>MAtt</FONT>
<DL>
<DD>----- Original Message -----
<DD>From:</B> <A href="mailto:sneeze@alphalink.com.au">Ryan Abbenhuys</A>
<DD>To:</B> <A
href="mailto:melbwireless@wireless.org.au">melbwireless@wireless.org.au</A>
<DD>Sent:</B> Monday, May 12, 2003 10:23 AM
<DD>Subject:</B> [MLB-WIRELESS] Melbwirelses DNS and Domain Names<BR><BR>
<DD>So, is there anything happening with regards to some sort of domain
<DD>structure on the network? Anyone from WGRouting&Addressing
looking at this
<DD>at the moment?<BR><BR>
<DD>I've started messing with domain names over our way. Now bear
with me here
<DD>because I don't know much about it or the terminology....<BR><BR>
<DD>Here's a few thoughts.<BR><BR>
<DD>We need something we all use that signifies we're melbwireless.
<DD>e.g. .wan .mw .melw<BR><BR>
<DD>then perhaps something to signify regional areas.
<DD>e.g. .oef (outer east&foothills) .inn (inner north) .cen
(central)<BR><BR>
<DD>so you'd end up with something say <A
href="http://www.wantirna-ap1.oef.mw">www.wantirna-ap1.oef.mw</A><BR><BR>
<DD>Now there's of course the other school of thought that we use domain
names
<DD>that fit in with the rest of the world. But my feeling is that this
comes
<DD>back we're going to need globaly routable IP's, etc then....And some
<DD>internet feeds, at which point you're looking at a wireless network
with
<DD>open internet access, which is playing with fire in my
opinion.<BR><BR>
<DD>What are other peoples thoughts/ideas?<BR><BR>
<DD>To unsubscribe: send mail to <A
href="mailto:majordomo@wireless.org.au">majordomo@wireless.org.au</A>
<DD>with "unsubscribe melbwireless" in the body of the message
</DD></DL></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>