ar-dns integration #47
Assignees
Labels
Comments
|
Anna - I am more than happy to support srv and txt records on ar-dns.net, but would need support from the reflector/gateway operators. |
|
Just discovered edge case, ar-net.org is un-available, but Internet otherwise is accessible.... Today (2020-08-21) ar-net.org is down (at least from my QTH) and thus the list of reflectors IP addresses is very out of date. |
|
Yeah the server physically failed during the move. I have to check an old
server and see if I have code.
…On Fri, Aug 21, 2020, 21:24 Kenny Richards ***@***.***> wrote:
Just discovered edge case, ar-net.org is un-available, but Internet
otherwise is accessible....
Today (2020-08-21) ar-net.org is down (at least from my QTH) and thus the
list of reflectors IP addresses is very out of date.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#47 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABR7I6RPE5SUGTWNXJOKEHTSB5B7RANCNFSM4DNMLTFA>
.
|
|
John,
If you’d like, I’m more than happy to pay for a list t3a.micro or something in AWS to run this. I’d surely give you an account with sudo.
—Anna
Sent from my iPad
On Aug 21, 2020, at 10:01 PM, John Hays (K7VE) <notifications@github.com> wrote:
Yeah the server physically failed during the move. I have to check an old
server and see if I have code.
On Fri, Aug 21, 2020, 21:24 Kenny Richards ***@***.***> wrote:
Just discovered edge case, ar-net.org is un-available, but Internet
otherwise is accessible....
Today (2020-08-21) ar-net.org is down (at least from my QTH) and thus the
list of reflectors IP addresses is very out of date.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#47 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABR7I6RPE5SUGTWNXJOKEHTSB5B7RANCNFSM4DNMLTFA>
.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I'll split the cost with Anna for the AWS instance.... I moved the WWARA site over and it was pretty painless. Kenny |
|
May take you up on it. Have to get the old server up and see if I have
everything.
…On Sat, Aug 22, 2020, 10:41 John D. Hays ***@***.***> wrote:
On Sat, Aug 22, 2020, 09:54 Kenny Richards ***@***.***>
wrote:
> I'll split the cost with Anna for the AWS instance....
>
> I moved the WWARA site over and it was pretty painless.
>
> Kenny
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#47 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABR7I6TJFQY2VTSFHBDT7CLSB7Z5PANCNFSM4DNMLTFA>
> .
>
|
|
NW Digital Radio would be happy to sponsor the server. What’s the cost?
Bryan
… On Aug 22, 2020, at 8:38 AM, Annaliese McDermond ***@***.***> wrote:
John,
If you’d like, I’m more than happy to pay for a list t3a.micro or something in AWS to run this. I’d surely give you an account with sudo.
—Anna
Sent from my iPad
On Aug 21, 2020, at 10:01 PM, John Hays (K7VE) ***@***.***> wrote:
Yeah the server physically failed during the move. I have to check an old
server and see if I have code.
On Fri, Aug 21, 2020, 21:24 Kenny Richards ***@***.***> wrote:
> Just discovered edge case, ar-net.org is un-available, but Internet
> otherwise is accessible....
>
> Today (2020-08-21) ar-net.org is down (at least from my QTH) and thus the
> list of reflectors IP addresses is very out of date.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#47 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABR7I6RPE5SUGTWNXJOKEHTSB5B7RANCNFSM4DNMLTFA>
> .
>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACDYY3XHGS35P7M5IUJJZMLSB7Q6TANCNFSM4DNMLTFA>.
|
|
Is this issue still being looked into. Is there an easy way to manually add Refelctors etc to the list. ? |
|
Ar-dns is deprecated.
…On Sat, Nov 5, 2022, 15:15 G7FCT ***@***.***> wrote:
Is this issue still being looked into. Is there an easy way to manually
add Refelctors etc to the list. ?
—
Reply to this email directly, view it on GitHub
<#47 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABR7I6ROUMOVMRKSYEUXOOTWG3L7ZANCNFSM4DNMLTFA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thanks for the reply. Don't have any other options on the Mac which is a shame. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The first stages of ar-dns.net integration are committed in f428fbb and 986199a. This is just a basic downloading of the preprocessed files that @johnhays provides. There are a few things to note about the entire system.
Buster's typedown functionality needs to have a complete list of at least reflector names so that it will work correctly. This can't really happen via DNS without AXFRs, which would be a pain to implement compared to the relatively painless implementation currently.
We may want to refresh those destination addresses periodically so that we get new information. I'm not exactly sure how to make this happen.
I have thoughts about using the plist files just to seed the dropdown lists, and then not updating them at runtime. Note with the current implementation, the new data is not saved to the disk. I think this is the right thing to do. Buster is inherently an Internet program, and I'm not going to pander to the edge cases where someone wants to use their ThumbDV non-Internet connected.
We could just refresh the information at some X time period and re-import the plist file. This would be relatively easy to do with GCD and the various timers available. We already do that with the various keepalives in the system, this wouldn't be that hard either. That being said, I think the right thing to do would be to do the DNS lookup for the address at link time not at startup time. When we get a link request, we know that the user intends to use the link, therefore refreshing the information is probably important. If the repeater or reflector has changed addresses since launch time, we should at least try to reflect that.
Moving forward, I'd really like to encode more information in ar-dns.net about things. Right now, I only really get name to DNS mappings and some crude idea of what protocols are supported. What I'd kinda like is to use SRV and TXT records to convey some more data. Maybe something like:
Anyhow, these are ideas and I'd love to hear from @johnhays especially on what he things, but input might also be useful from @richark and @DonaldHays as well.
The text was updated successfully, but these errors were encountered: