[MLB-WIRELESS] DNS......READ THIS!

[John McClumpha]

so put together a dns that "works for now" on some servers that "work 
for now" running some services that "work for now" on a network that 
"works for now"....

ok... /cynicism

sorry - might have got a bit carried away - but I don't see the point in 
   devising systems with (potentially) in-built redundancy.

I'm glad that there has been *something* setup for DNS - but it appears 
that you and a handful of others are using this system, and there are 
other nodes using other systems.

I agree that getting too far ahead of ourselves can slow things down - 
and it's much better to see something put into action than just lots of 
waffle about it.

Please - keep using your DNS - but I can't say I'm fully convinced that 
this is the best system

Admittedly Im not connected to any other nodes permanently - but as of 
tomorrow night (when we erect the mast!) things should all be good. A 
small group of us in Narre Warren are putting together a great little 
network with various services & features to share - which we'll happily 
share with the rest of you if we can get a reliable link going.

I wasn't suggesting that one group make a decision for all others - but 
rather we *communicate* about things.

Like I've stated previously - I'm not aware of the background of the DNS 
systems that have been discussed or setup - this is simply my personal 
opinion - I'd like to find out more if anyone's willing to discuss it?

may I ask again:
 >>Has this naming convention been set in stone by the committee or is it
 >>just one that has got "off the ground"?


john
node INQ

Ryan Abbenhuys wrote:
> Nice idea in theory....but I can't see it happening.
> 
> The problem is other wireless groups won't take kindly to one group making
> a decision like that.  The other issue is that other wireless groups
> already have other DNS systems, some similar to this one. Another issue is
> that we really shouldn't be thinking about linking interstate when we
> aren't linked up within the state.
> 
> There's a lot of getting ahead of ourselves which results in nobody making
> a decision in the end and nothing progressing at all.  Part of the reason I
> have become so jaded.
> 
> With the mwnode.com DNS setup, it took nothing to setup, it works for
> everyone, it's very simple.  Until such time as someone can show the group
> another system that works and an actual *need* for another system, why
> bother?
> 
> I had a draft of another DNS system ready to go sometime ago that would
> have also worked but was more involved.  I came to the conclusion that I
> could put the idea out there and people would say great stuff, but nothing
> was ever going to happen.  So mwnode.com happened overnight and it does the
> job fine.
> 
> So my opinion would be to just keep using it until there is good reason to
> change.  Concentrate on other things such as getting active services on the
> network, working on better routing design, and more links between groups. 
> It's all very well to have a free wireless network but if nobody does
> anything with it what's the point? (pings don't count)
> 
> 
> 
> 
>>Hi Ryan,
>>
>>thanks for the info - I was unaware of such a system already in place.
>>
>>My only thought is that the naming convention is very specific to 
>>*melbourne*wireless - at present this doesn't matter - however if (when) 
>>melb wireless manages to spread its wings and connect with one of the 
>>interstate networks things may be a little different. I would have 
>>though a more generic, national naming convention would be the best
> 
> option?
> 
>>keep in mind I am simply sharing my thoughgts on this - I am unaware of 
>>the history of this to date (as, it would seem, are many others).
>>
>>Has this naming convention been set in stone by the committee or is it 
>>just one that has got "off the ground"?
>>
>>john
>>node INQ
>>
> 
> 
> .
> 

To unsubscribe: send mail to majordomo at wireless.org.au
with "unsubscribe melbwireless" in the body of the message