My thoughts on this:<br><br>Q1 - I think using <a href="http://wireless.org.au">wireless.org.au</a> as the "root" is the best option here. If things take off for a "free" national wifi network down the track, then as you say, it'll be easy to bring other cities on board.<br>
- in addition to WWW, also disallow FTP and SSH (and other short 3 letter acronyms) WWW the most obvious, but I think other short "3" letters that are known to those that have dabbled even the tinniest bit in linux, not so much used but just looked at for a bit before going "too hard" and back to windows. Is it possible someone can block these on the MW website? Will it require renewed interest in maintaining the actual website and upgrading some functions within it? IE: The creation of node names.<br>
<br>Q2 - It does make things rather long, so perhaps internally set it up as "kct.melbourne.wireless" "kdj.geelong.wireless" as a base level design. That would map with internal and external easy enough. If it cannot find "kdj.geelong.wireless" it will automatically map itself to "<a href="http://kdj.geelong.wireless.org.au">kdj.geelong.wireless.org.au</a>" and bounce the user out their normal internet connection (assuming they have one).<br>
<br>Q3 - Making it easy would be to possibly give the user the steps for WinXP / Vista / (god forbid) 95 & 98 / MAC / Linux / <insert flavour of linux> to add an IP as a their first port of call. Based on location. The main DNS hosting should be done by users who have some understanding (or at least willing to supply the required access to a hosted service in their locale) for DNS resolution.<br>
<br>I'm sure, someone with some smarts can construct a web-page that will generate a script the end-user can run to insert the appropriate information. Perhaps have a tiny, Tiny, TINY 3rd party app that will go "oh you want something on the internal wireless? Go HERE!" and redirect them to the local DNS for their locale.<br>
<br><br>As I said, this WILL require the co-operation of various users in various locales, that while they may not have the smarts to operate a feature themselves, are willing to donate the use of hardware they might be able to have dedicated turned on at their home.<br>
<br>It won't be foolproof, but I think it may be one of the easier solutions.<br><br>Means should ballarat.wireless drop off from connection to the greater wireless network, anyone there can still resolve their internal network with little issue.<br>
<br><div class="gmail_quote">On Tue, Mar 24, 2009 at 8:30 PM, Russell Smith <span dir="ltr"><<a href="mailto:mr-russ@pws.com.au">mr-russ@pws.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
I know we don't have any firm answers on who controls the melbourne wireless domains on the internet. But that does not stop use deciding on what we are doing going forward on the internal DNS resolution.<br>
<br>
The two pages on the wiki are;<br>
<a href="http://www.melbourne.wireless.org.au/wiki/?DNSConvention" target="_blank">http://www.melbourne.wireless.org.au/wiki/?DNSConvention</a><br>
<a href="http://www.melbourne.wireless.org.au/wiki/?DNS" target="_blank">http://www.melbourne.wireless.org.au/wiki/?DNS</a><br>
<br>
Both of these appear quite old and don't have any future direction or people setting them up :) I don't like what's presented in DNSConvention and have outlined a proposal below for comment.<br>
<br>
<br>
We gave two domains for melbourne wireless. One <a href="http://wireless.org.au" target="_blank">wireless.org.au</a>, one <a href="http://melbournewirless.org.au" target="_blank">melbournewirless.org.au</a>.<br>
<br>
<a href="http://melbourne.wireless.org.au/" target="_blank">http://melbourne.wireless.org.au/</a><br>
<a href="http://melbournewireless.org.au/" target="_blank">http://melbournewireless.org.au/</a><br>
<br>
For portability and the ability to map all wireless networks into one DNS space, <a href="http://wireless.org.au" target="_blank">wireless.org.au</a> would be good to continue to use. If we connect to other states, we can have <a href="http://adelaide.wireless.org.au" target="_blank">adelaide.wireless.org.au</a> or even <a href="http://geelong.wireless.org.au" target="_blank">geelong.wireless.org.au</a>. For setting up DNS it needs to be decided which domain we are going to use as a base.<br>
<br>
Q1: What are your thoughts?<br>
<br>
I think the best option is to use <a href="http://wireless.org.au" target="_blank">wireless.org.au</a> for everything. It along with the fact I believe a root domain complicates life and doesn't allow you to easily run internal and external facing websites with the same DNS name.<br>
<br>
1. Other cities can come on board with that same domain name. eg <a href="http://adelaide.wireless.org.au" target="_blank">adelaide.wireless.org.au</a>, <a href="http://geelong.wireless.org.au" target="_blank">geelong.wireless.org.au</a><br>
2. We can resolve names to varying lengths of short when inside the network. in melbourne; <a href="http://gw.kct/" target="_blank">http://gw.kct/</a> is my gateway, for geelong it's;<br>
<a href="http://gw.abc.geelong/" target="_blank">http://gw.abc.geelong/</a><br>
3. Easy forwarding to other DNS servers, don't need to query root and do<br>
recursive.<br>
4. Easy setup, no mucking with roots, complicated forwarding and the like.<br>
5. Split DNS. You can allow internet clients to resolve certain nodes<br>
if we like, eg; <a href="http://gw.kct.melbourne.wireless.org.au/" target="_blank">http://gw.kct.melbourne.wireless.org.au/</a><br>
<br>
possible downsides are;<br>
1. need to disallow creation of a www node as people will assume it's the website. And it is externally.<br>
2. You need to maintain the DNS both on the Internet and on MW for the relevant external records. eg mail, www<br>
<br>
Q2: Is this a good format and what format would you propose/support?<br>
I know Mike has suggested <a href="http://www.kct.node.melbourne.wireless.org.au/" target="_blank">http://www.kct.node.melbourne.wireless.org.au/</a><br>
<br>
I expect we would set MW clients to set their DNS to the internal DNS server and receive all of their DNS resolution through MW. As far as I'm aware it's going to be very difficult to make it any easier for your average user to connect and get DNS resolution.<br>
<br>
Q3: Ideas about making DNS easy for clients?<br>
<br>
<br>
I'd also say <a href="http://melbournewireless.org.au" target="_blank">melbournewireless.org.au</a> should be a 301<br>
redirect to <a href="http://www.melbourne.wireless.org.au" target="_blank">www.melbourne.wireless.org.au</a> so you are using consistent<br>
names both inside and outside the network for our website.<br>
<br>
The only configuration that's required at the client end is the add the<br>
following into their DNS suffixes.<br>
<br>
You would add; <a href="http://melbourne.wireless.org.au" target="_blank">melbourne.wireless.org.au</a> <a href="http://wireless.org.au" target="_blank">wireless.org.au</a><br>
That can be done on the dhcp server or on the client. And instantly you can resolve all short names.<br>
<br>
Q4: Anything else to contribute?<br>
<br>
Regards<br>
<br>
Russell<br>
<br>
_______________________________________________<br>
Melbwireless mailing list<br>
<a href="mailto:Melbwireless@wireless.org.au">Melbwireless@wireless.org.au</a><br>
<a href="http://wireless.org.au/mailman/listinfo/melbwireless" target="_blank">http://wireless.org.au/mailman/listinfo/melbwireless</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Victor ('Daworm')<br>Melbourne Wireless Node: KDJ & KDT<br>AoCWiki Sysop (<a href="http://aoc.wikia.com/">http://aoc.wikia.com/</a>)<br>