Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
ar-dns integration #47
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.
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: