[Flightgear-devel] TerraSync DNS problem

[James T. <ja...@fl...>]

Just to add excitement to the issues around TerraSync right now, my ISP has helpfully exposed an additional issue, which might be affecting some people: our DNS query is not switching to TCP when it’s required.

As we add more data to our NAPTR record, for mirrors and for OSM2City (and WS3 scenery, soon), the record size now exceeds UDP limits (sort of) My ISP is truncating the UDP DNS query. Most DNS clients then switch to TCP and retry the request (there is no size limit for TCP, of course), but our current code isn’t doing that. So we need to figure out where / how we support that, and in the meantime if you see (or hear of someone) getting lots of this:

 15.60 [ALRT]:terrasync  Warning: no DNS entry found for 'terrasync.flightgear.org' 'ws20'
   15.60 [ALRT]:terrasync  Warning: no DNS entry found for 'terrasync.flightgear.org' 'o2c'
   15.60 [ALRT]:terrasync  Warning: no DNS entry found for 'terrasync.flightgear.org' 'ws20'
   15.60 [ALRT]:terrasync  Warning: no DNS entry found for 'terrasync.flightgear.org' 'o2c'
   15.60 [ALRT]:terrasync  Warning: no DNS entry found for 'terrasync.flightgear.org' 'ws20'
   15.60 [ALRT]:terrasync  Warning: no DNS entry found for 'terrasync.flightgear.org' ‘o2c'


… now you know why :)

Kind regards,
James