[HamWAN PSDR] hamwan.net DDNS [was: hostname on ampr.org?]

[Dean Gibson AE7Q]

On 2014-03-30 23:46, Bart Kus wrote:
>
> BTW, I believe this is the longest email I've written in over a year.  
> Gotta knock that off.  :)
>
> --Bart

Yep, and it's getting nearly too long to be read, so in this eMail, I'll 
address snippets here, and in a separate eMail, address evangelization.

> On 3/30/2014 5:42 PM, Dean Gibson AE7Q wrote:
>> *...**  Hopefully, things are not going to be so dynamic in HamWAN 
>> that hamwan.net DNS servers are going to be constantly on the move.* 
>
> No need to worry about changes here.  HamWAN authoritative DNS servers 
> shall forever and always(*) be on 44.24.244.2 and 44.24.245.2.  These 
> are anycast IPs from 2 different anycast ranges.

Good!

>
> ... The BIND choice isn't about scalability, it's about stability.  I 
> can take you through some awesome BIND failures I've seen over the 
> years.  Let's do that not-in-this-email though.

No need; I've multiple Windows and Linux systems, and the only 
successful attack I've ever experienced was in 1991, in BIND.  I was 
just mentioning BIND because I've familiar with its capabilities with 
regard to DDNS (direct/manual, or via the DHCP server). Hopefully any 
replacement has the same capabilities.

> ... To help users cope with all the changes and exposed complexity 
> happening right now, we're suggesting the shared administration 
> model.  Since you chose not to participate in that, you need to keep 
> up on your own.  I would also point out that you allow Comcast or 
> whoever your ISP is to manage your modem, since they don't even give 
> you a choice.

Frontier (was Verizon), but the same issue.  That's why I run a DMZ.  
Exterior administrative access (whether Comcast, Frontier, or HamWAN) is 
always a giant target.

> ... You've also made it harder on yourself by disallowing remote 
> access for network operator folks.  That's a personal choice you're of 
> course free to make with your hardware, but I think it's safe to say 
> we're not gonna stop pushing for our goals to keep the complexity 
> you're chosen to take on, low.
>
> ... What are we blocking in your tinkering?  The two examples you 
> mentioned (DNS and static IP) we can address right now.  DNS we can do 
> by hand, and static IP is fairly static for you even with just DHCP.  ...
>
> What kind of tinkering are you thinking of doing?  Perhaps some of 
> that information might drive some inputs to our design plans.  I'd 
> like to know how people use the network in general.

What do you mean, "What kind of tinkering are you thinking of doing?"?  
I have no real idea;  that's why we call it "tinkering" !!!

Probably the first thing I'd do, would be to set up another amateur 
radio oriented web site;  that's one reason for a DNS hostname served 
off of a 44.x.x.x DNS server.  I have three web sites now that are 
devoted to amateur radio (www.ae7q.com, www.ae7q.net, and 
www.dstardb.com).  I received 
http://www.yasme.org/news_release/2013-12-18.pdf ($1000) for the first 
web site.  These web sites need to be available to the general amateur 
population (hence remaining where they are on the Internet), but I might 
set up a more specialized one on the 44.x.x.x network. I'd suspect this 
would be a common interest in HamWAN.  Right now, anyone setting up a 
web site on the 44.24.240.x network is subject to IP address changes 
without a hostname being used to hide the issue.

There's no rush in solving this;  I need to move ae7q.net content (and a 
number of eMail addresses) over to ae7q.com in preparation for using 
ae7q.net on 44.x.x.x anyway.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.hamwan.net/pipermail/psdr/attachments/20140331/3898d66f/attachment.html>