Catching up with responses I missed (that seem largely unhelpful)...
Update - after PlusNet have forced 10.2.5.2 FO on me, I've redone my test and without specifying DNS server and just relying on the router, resolution seems to work now...
nslookup lux.smtp-out.eu-west-1.amazonses.com
Server: dsldevice.lan
Address: 192.168.1.254
Non-authoritative answer:
Name: lux.smtp-out.eu-west-1.amazonses.com
Addresses: 176.32.127.139
176.32.127.205
176.32.127.137
176.32.127.202
176.32.127.203
176.32.127.201
176.32.127.200
176.32.127.138
176.32.127.141
176.32.127.136
176.32.127.204
176.32.127.140
176.32.127.206
176.32.127.143
176.32.127.207
176.32.127.142
However as I feared, the firmware update has broken things. General DNS resolution it seems! (see
here).
Just to stress though, the original issue was clearly a router firmware issue. Absolutely nothing to do with Windows. That other routers have the issue, well sure. Routers have all kinds of issues. Many firmware are based on common code sources. Big deal. The issue was still in this case with the TG582n FTTC router as supplied by PlusNet and the 8.C.M.0 firmware.
