Short answer.... no. There's no way as Dual DHCP DNS (DDD) server does not support TCP requests.
Longer answer:
Usually client requests come as a UDP packet and most responses fit within the 512bytes limitation. However there are clients that know/assume the responce is going to be larger than 512bytes and use TCP instead (clairvoyant or bad coding?). Note; TCP is used by DDD for zone transfers, just not requests from clients.
In my case it was several Firestick's, running NetFlix, where Netflix was asking for an address to one of streaming services. Seems they were expecting an IPv6 address or something large and used TCP, rather than UDP. Interestingly, the next request from Netflix was a UDP request that DDD resolved and delivered perfectly.
Neil
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What does this really mean and is there any way to avoid it?
I have a number of host IPs in the log file that send this message out.
Thanks
Tim,
Short answer.... no. There's no way as Dual DHCP DNS (DDD) server does not support TCP requests.
Longer answer:
Usually client requests come as a UDP packet and most responses fit within the 512bytes limitation. However there are clients that know/assume the responce is going to be larger than 512bytes and use TCP instead (clairvoyant or bad coding?). Note; TCP is used by DDD for zone transfers, just not requests from clients.
In my case it was several Firestick's, running NetFlix, where Netflix was asking for an address to one of streaming services. Seems they were expecting an IPv6 address or something large and used TCP, rather than UDP. Interestingly, the next request from Netflix was a UDP request that DDD resolved and delivered perfectly.
Neil
Thanks for the great explination.