MIME-Version: 1.0 In-Reply-To: X-Mailer: MIME-tools 5.428 (Entity 5.428) Content-Disposition: inline References: Content-Type: text/plain; charset="UTF-8" Message-ID: Content-Transfer-Encoding: binary X-RT-Original-Encoding: utf-8 RT-Send-CC: Content-Length: 567 I don't think there is anything for us to do here. The authoritative server is breaking too many DNS fundamentals to interoperate. If it set tc=1 it might be worth hacking around the broken EDNS support but to fix this we would also have to figure out tc=1 should have been set or force TCP for these servers. Add to that there is a updated version of the server available I think the best solution is to accept the odd report like this and encourage the authoritative server to upgrade. Note they have introduced a CNAME since the report was first published.