<html>
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 type=cite class=cite 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
</dl></blockquote></html>