[arm-allstar] DNS server for HamVoip

Don Backstrom AA7AU z-armallstar at deliberate.net
Sat Dec 30 12:14:12 EST 2017


On Fri 29-Dec-17 23:10, "Doug Crompton via arm-allstar" wrote:
> We have out own DNS server as
> part of hamvoip that accesses the root servers directly.

	Thanks for posting that, Doug. May I ask a couple of questions for 
clarification please?

1) Are you referring to a remote separate DNS server, or a built-in DNS 
server running locally?

2) Which "root servers" are you referring to?

3) Has your DNS-lookup approach for node IP# now fully replaced the 
regular repetitive node-list download cycle using the AllStarLink server 
(which increases bandwidth use and server load over time)?

4) If so, is there now that savings in initial start-up time as a result 
compared to the old registration cycle lag?

5) Is this bit using the <node#>.asnode.org structure? If not, where is 
that from? If so, how often is that DDNS updated?

6) Can we rely upon the asnode.org setup to remain in place, and usable, 
from now forward, and therefore not need the use of our own 
ddclient/DDNS setups for these AllStar node PIs?

7) Is your new DNS sever logic cache-based or does it lookup every time 
a remote node# is referenced (like connect, monitor, etc)? If so, could 
you explain a bit about that?

8) <rhetorical> Is there a way to force new users to read the 
documentation first, or is this, like all system-related stuff, always a 
repeat of Ground Hog Day? </rhetorical>

	TIA!

	Best Wishes for a Happy, Healthy, and Prosperous New Year ...
and a big *THANK YOU* to you and David for all that you've done.

	- Don - AA7AU


More information about the arm-allstar mailing list