[MLB-WIRELESS] Melbwirelses DNS and Domain Names

[Fenn Bailey]

On this note, I think it would be nice if we had (at least) dual forward
resolves:
 
fdf.wan.melbourne.wireless.org.au + 
fdf.south-melb.wan.melbourne.wireless.org.au 
 
But have our reverse resolution be verbose (eg: the full location). This
would make traceroutes more meaningful (not to mention really cool!)
 
    Fenn.

-----Original Message-----
From: owner-melbwireless at wireless.org.au
[mailto:owner-melbwireless at wireless.org.au] On Behalf Of Matt
Sent: Monday, 12 May 2003 11:27 AM
To: Melbourne Wireless; Routing Workgroup
Subject: Re: [MLB-WIRELESS] Melbwirelses DNS and Domain Names


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. 

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.

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.

2c more
Matt



At 10:52 AM 12/5/2003 +1000, Matthew Hill wrote:


Ryan and all
 
This is what i wanted to bring up a while ago and they werent interested.
 
This is similar to what perth suggests, and what your suggested in your
example, rocks. Exactly what is possbily should be. 
 
www.wantirna-ap1.oef.mw says exsactly where it is, 
 
www.thebigfella.peninsula.mw that would be mine ...
 
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.
 
Cheers
 
MAtt 

----- Original Message ----- 

From: Ryan Abbenhuys <mailto:sneeze at alphalink.com.au>  

To: melbwireless at wireless.org.au 

Sent: Monday, May 12, 2003 10:23 AM 

Subject: [MLB-WIRELESS] Melbwirelses DNS and Domain Names



So, is there anything happening with regards to some sort of domain 

structure on the network?  Anyone from WGRouting&Addressing looking at this 

at the moment?



I've started messing with domain names over our way.  Now bear with me here 

because I don't know much about it or the terminology....



Here's a few thoughts.



We need something we all use that signifies we're melbwireless. 

e.g.  .wan  .mw  .melw



then perhaps something to signify regional areas. 

e.g. .oef (outer east&foothills) .inn (inner north) .cen (central)



so you'd end up with something say www.wantirna-ap1.oef.mw



Now there's of course the other school of thought that we use domain names 

that fit in with the rest of the world. But my feeling is that this comes 

back we're going to need globaly routable IP's, etc then....And some 

internet feeds, at which point you're looking at a wireless network with 

open internet access, which is playing with fire in my opinion.



What are other peoples thoughts/ideas?



To unsubscribe: send mail to majordomo at wireless.org.au 

with "unsubscribe melbwireless" in the body of the message 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wireless.org.au/pipermail/melbwireless/attachments/20030512/fb94bb85/attachment.html>