MHS1 continously asking DNS resolution of www.google.com
I manage my own internal DNS server to resolve my LAN names/addresses and to forward public queries outside of my LAN. I noticed that the MHS1 (ip address 192.168.1.40) sends two queries each 3 seconds to the dns server (192.168.1.10) to resolve http://www.go0gle.com:
16-Jul-2021 10:31:51.522 client @0xffff9004a300 192.168.1.40#38650 (www.google.com): view internal: query: http://www.google.com IN A + (192.168.1.10)
16-Jul-2021 10:31:51.522 client @0xffff90000c80 192.168.1.40#38650 (www.google.com): view internal: query: http://www.google.com IN AAAA + (192.168.1.10)
16-Jul-2021 10:31:54.572 client @0xffff98053540 192.168.1.40#54146 (www.google.com): view internal: query: http://www.google.com IN A + (192.168.1.10)
16-Jul-2021 10:31:54.572 client @0xffff9804fac0 192.168.1.40#54146 (www.google.com): view internal: query: http://www.google.com IN AAAA + (192.168.1.10)
16-Jul-2021 10:31:57.642 client @0xffff9804fac0 192.168.1.40#54704 (www.google.com): view internal: query: http://www.google.com IN A + (192.168.1.10)
16-Jul-2021 10:31:57.642 client @0xffff98053540 192.168.1.40#54704 (www.google.com): view internal: query: http://www.google.com IN AAAA + (192.168.1.10)
16-Jul-2021 10:32:00.692 client @0xffff940782f0 192.168.1.40#52242 (www.google.com): view internal: query: http://www.google.com IN A + (192.168.1.10)
16-Jul-2021 10:32:00.692 client @0xffff94000c80 192.168.1.40#52242 (www.google.com): view internal: query: http://www.google.com IN AAAA + (192.168.1.10)
16-Jul-2021 10:32:03.742 client @0xffff90000c80 192.168.1.40#57733 (www.google.com): view internal: query: http://www.google.com IN A + (192.168.1.10)
16-Jul-2021 10:32:03.742 client @0xffff9004a300 192.168.1.40#57733 (www.google.com): view internal: query: http://www.google.com IN AAAA + (192.168.1.10)
16-Jul-2021 10:32:06.792 client @0xffff94000c80 192.168.1.40#44923 (www.google.com): view internal: query: http://www.google.com IN A + (192.168.1.10)
16-Jul-2021 10:32:06.792 client @0xffff940782f0 192.168.1.40#44923 (www.google.com): view internal: query: http://www.google.com IN AAAA + (192.168.1.10)
16-Jul-2021 10:32:09.852 client @0xffff8c042330 192.168.1.40#49938 (www.google.com): view internal: query: http://www.google.com IN A + (192.168.1.10)
16-Jul-2021 10:32:09.852 client @0xffff8c038840 192.168.1.40#49938 (www.google.com): view internal: query: http://www.google.com IN AAAA + (192.168.1.10)
16-Jul-2021 10:32:12.902 client @0xffff9004a300 192.168.1.40#34701 (www.google.com): view internal: query: http://www.google.com IN A + (192.168.1.10)
16-Jul-2021 10:32:12.902 client @0xffff90000c80 192.168.1.40#34701 (www.google.com): view internal: query: http://www.google.com IN AAAA + (192.168.1.10)
I know that the result is cached so nothing goes out of LAN, but I think that MHS1 should not do that to avoid a useless use of network.
TY for any advice about this problem
You must be logged in to reply to this topic.
0 reply 
1 participant