I dug a little more with wireshark.  The dns for saildocs never returns a result from the go.

Adding the saildocs.com to the hosts file fixed the problem.

Its more of a workaround to the issue that DNS lookups are not working,
Caveat being if the IP address for any of these services change it could cause worse problems.

The problem i encountered, was that DNS resolution does not seem to work for me through the iridium go
This prevents expedition from being able to connect to any services it is not calling by IP address.

I can see the DNS lookup request get sent, but no response comes back,  This is with the default iridium go settings, and dns forwarding enabled. (disabling dns forwarding did not seem to work either). I did not try to force a custom DNS server, choosing to update the hosts file instead.

To implement the workaround
You will need to run a text editor like notepad as administrator
then open this file
c:\Windows\System32\Drivers\etc\hosts
at the bottom of the file, add these lines, 
#----------------ADD BELOW THIS -------------------------20.119.16.59    expeditionmarine.com 20.119.16.59    www.expeditionmarine.com 44.193.104.173  saildocs.com  51.255.36.105   grib-server.greatcircle.be 178.79.175.12   yb.tl 
#------------------- DONT ADD THIS OR ANYTHING BELOW ----------------
Save the file, then windows will look at those files when it tries to locate the host names before asking a DNS server the IP addressed were grabbed from the help file.  If any of these IP addresses ever change, the line for the host will need to be changed to the new IP address

Hopefully a better solution to allow DNS lookups through the go will be found.

Additional note.  These settings are not unique to expedition.  They will apply to all applications.
Hope this helps someone 

-tim
 

Tim, Nick,
That worked for me on a windows 10 tablet.  I also had to turn off the firewall or otherwise allow expedition access.  Thanks for sharing the details of how to update the hosts file.
-afu

I have been testing, but don't have a better solution than the above.

I also tested an old version of Exp and see the same issue. My suspicion is something has changed in Iridium.

There is a new version of Exp, but I still still see the same behaviour. Ymmv.
 
SquidX works here, but it points to a fixed address. Predictwind fails here too.

This may be use use  https://sailmail.com/iridium-go-troubleshooting/

Update for Iridium GO posted.

This supports the Expedition Grib server, saildocs, YB Tracking and SailFlow. No Squid as there seem to be certificate issues, but there is SquidX.

This may also be of use to Iridium handset users.