So, I wrote a new server, which I run myself. It requested the callsign list from Robin's server, and "cached" it. If Robin's server became unavailable, it would keep the cache, until Robin's server would return, etc. This has worked well.

Later, after we added the "inbound connections" feature to DVAR Hotspot, I added the registration feature to the server (and DVAR of course), so that if people use my server, AND they have "inbound connections" enabled (meaning: their Hotspot can be connected to from the outside, like a normal gateway), they would let the server know, and so they would appear in the gateway list.

This feature has been present in DVAR Hotspot since 2.39, but we didnt make it standard until now, after we have discussed this (and other issues) with Robin. After all, extensions are good, but only if they do not break things!

One thing to remember is, that this server does not "replicate back" to Robin's server. So, registered hotspots are not (and will not be) visible on Robin's server, as his server ONLY handles full-size D-Plus gateways.

So.. indeed. DPNS (our server, D-Plus Name Server) was launched publicly, and it's a major success!  Many, many hotspots, DV Dongles and DVAP's are using it worldwide. Somehow it feels like we are now used as a HAMskype kind of system :)

What? Did I just say "DV Dongles"?

Yes, I did.  Although this has not been formally implemented in the DVtool software yet, you can use a little trick to tell the DVtool software to use the new software. This trick is to add the following lines to your C:\WINDOWS\System32\Drivers\ETC\hosts file:

188.203.83.181 dstarns.opendstar.org opendstar.org dstarns
188.203.83.181 dstarns.opengateway.org dvtool.opengateway.org opengateway.org
188.203.83.181 dstarns.dstargateway.org dvtool.dstargateway.org dstargateway.org