Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Changes

Jump to: navigation, search

DNS

4,926 bytes removed, 20:40, 13 November 2016
Remove mailing list quotes without information content for this page.
== Status ==
Torsten created a branch {{flightgear source|b=topics/mpdiscovery-via-dns|t=branch}} with a first implementation - just in case somebody might want to have a look. It does contain full lookup of a server list by checking the SRV records and each server's properties via TXT records with name=value text and value being a base64-encoded<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35480316/
|title = <nowiki> Re: [Flightgear-devel] base64 decoding in c++? </nowiki>
|author = <nowiki> James Turner </nowiki>
|date = Nov 9th, 2016
|added = Nov 9th, 2016
|script_version = 0.40
}}</ref> JSON string. It does not /yet/ contain a "is-online" check.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35482909/
|title = <nowiki> Re: [Flightgear-devel] Proposal for storing the mp server
information in DNS instead of a web service </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Nov 10th, 2016
|added = Nov 10th, 2016
|script_version = 0.40
}}</ref>
 
The latter being considered to be implemented using UDP ‘ping’, i.e. because we can include some interesting info in it.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35483816/
|title = <nowiki> Re: [Flightgear-devel] Proposal for storing the mp server
information in DNS instead of a web service </nowiki>
|author = <nowiki> James Turner </nowiki>
|date = Nov 10th, 2016
|added = Nov 10th, 2016
|script_version = 0.40
}}</ref>
 
Torsten has meanwhile created the necessary DNS entries for the flightgear.org domain. The topics/mpdiscovery-via-dns branch should now be fully functional and discover the required multiplayer servers using DNS. It might take until Sat, 12th 00:00 UTC before the TTL of the old records have expired and your nameserver pulls in the changes.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35485218/
|title = <nowiki> Re: [Flightgear-devel] Proposal for storing the mp server
information in DNS instead of a web service </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Nov 11th, 2016
|added = Nov 11th, 2016
|script_version = 0.40
}}</ref>
 
== Usage of DNS within FlightGear ==
|script_version = 0.40
}}</ref>.
 
Its creation was inspired by a discussion that took place on the FlightGear devel mailing list in 11/2016 to stop using a dedicated web service for retrieving a list of active multiplayer servers and instead use DNS <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35482909/
|title = <nowiki> Re: [Flightgear-devel] Proposal for storing the mp server
information in DNS instead of a web service </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Nov 10th, 2016
|added = Nov 10th, 2016
|script_version = 0.40
}}</ref>, the idea of storing the information about multiplayer server in DNS instead of providing those through a web service. The motivation behind is to remove another single point of failure. If the current service goes away for some reason, the current implementation falls back to a hardcoded list of multiplayer servers. We consider DNS as an "always-on" service and already use it for looking up a mirror for terrasync<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35475777/
|title = <nowiki> [Flightgear-devel] Proposal for storing the mp server information
in DNS instead of a web service </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Nov 7th, 2016
|added = Nov 7th, 2016
|script_version = 0.40
}}</ref>
== FlightGear systems using DNS ==
decodes to
{"name":"mpserver01","location":"Frankfurt,Germany"}
 
Any FGMS changes will likely be quite small, but it would be good to ensure the ‘main network’ is relatively close to current versions. In a perfect would we would have an automated system to update the servers (any thoughts on ideas how to achieve that? Doesn’t need to be smart, could be as simple as git pull; make; make check -> if it passes make install; restart fgms) <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35488212/
|title = <nowiki> Re: [Flightgear-devel] Proposal for storing the mp server
information in DNS instead of a web service </nowiki>
|author = <nowiki> James Turner </nowiki>
|date = Nov 13th, 2016
|added = Nov 13th, 2016
|script_version = 0.40
}}</ref>
 
 
All our currently available mpserver seem to be running *nix[1], so indeed a cron'ed procedure [...] should be easy to implement<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35488265/
|title = <nowiki> Re: [Flightgear-devel] Proposal for storing the mp server
information in DNS instead of a web service </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Nov 13th, 2016
|added = Nov 13th, 2016
|script_version = 0.40
}}</ref>
== References ==

Navigation menu