Forum Discussion
Suspicious DNS Activity Originating from GTM Name Server
Hi All,
We are seeing continuous TCP packet reset error at client side from 3DNS name server. Search on GTM log & taken packet capture but no clue where rest packet is generating. From searching Google for similar issues, this seems to be related to an outdated/mis-configured Bind DNS server. Need your suggestion to close case.
Jan 05 00:04:51 x.x.0.100 named[23726]: dispatch 0x7ff06c4f4650: shutting down due to TCP receive error: xx.x.x.x53: connection reset
Jan 05 00:11:37 x.x.0.10 named[13320]: dispatch 0x7f78570f5ad0: shutting down due to TCP receive error: xx.x.x.x53: connection reset
Jan 05 00:14:14 x.x.0.10 named[13320]: dispatch 0x7f78570f5ad0: shutting down due to TCP receive error: xx.x.x.x53: connection reset
Jan 05 00:05:55 199.120.69.22 named[21101]: dispatch 0xb5436788: shutting down due to TCP receive error: xx.x.x.x53: connection reset
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com