Comment 7 for bug 1245179

.... my bad, even clearing the error wouldn't work, as one of the later attempts may still set it (I've already forgotten what I was thinking when I made that fix...). That fix is part of the latest stable versions of AirDC++ and AirDC++ nano so I consider it to be reliable. The version URL used by AirDC++ has A and AAAA records which makes noticing such errors easy (even though I missed this bug first because I have IPv6 connectivity on every Linux machine...).