Hi, Could someone validate the explanation given in 2007 (3rd post) https://community.barracudanetworks.com/forum/index.php?/topic/8683-icmp-destination-unreachable-to-dns-server/ for the last ICMP packet in the DNS trace? I am seeing similar behavior on a Windows client. https://www.dropbox.com/s/aef1rbjuj5lz1bj/dns_icmp.pcapng?dl=0 Windows Client - 192.168.30.124 Windows DNS Server - 192.168.30.5 Thank you asked 11 Oct '16, 08:53 net_tech |
One Answer:
I totally agree with that explanation. The DNS client's timeout for arrival of a DNS response does exist, and in your case it is shorter than the server's response time. After expiration of that timeout the client unbinds from the socket, causing If you are interested in details, you can create a batch file like
run it with output redirected to a file and initiate, from another window, the DNS query which you know will fail this way. In the output file, you should see for how long the DNS client keeps the socket open. answered 11 Oct '16, 11:12 sindy |