0
We are experiencing network drops on our (small) company network. The computers are all connected wired and the drops seem to be internal and external.
We have a simple DNS
installed on our PC's for a loop back for addresses like lc.*
to develop multiple websites without needed to change the host file for each url. There is no caching on this server and other request are forwarded to our providers DNS
. This works as I can connect to all websites/services without any delay.
But mostly when using a RDP
connection I get regular timeouts and after a few seconds it connects again. This happens when I'm at work and connect to external servers, or when i'm working offsite and connect to my work computer.
We hired somebody to check the network and he says the timeouts are because of the DNS
server. He even says most slow network problems are because of DNS
issues, which I can understand if the initial connection is slow. His advice is to use a direct IP
instead of a host name, to solve the drops.
But as far as I know, once a connection has been made, the DNS
server is no longer used. And when I connect from offsite to my work computer, it doesn't matter at all what DNS
my work computer uses.
Could a DNS
setting cause network drops after the connection has been made? Or is it indeed no longer used once we know example.com
can be found at 93.184.216.34
?
re: RDP and TCP - that is not 100% true :) With version 8.0 of the RDP protocol, Microsoft introduced UDP support for connections (see here: https://support.microsoft.com/en-us/help/2592687/remote-desktop-protocol-rdp-8-0-update-for-windows-7-and-windows-serve ). But even with UDP, it does not do DNS lookup for every packet. Re: the rest - yes, you are 100% correct, the issue does not sound as DNS as that is a 1 time thing (and the OS then caches the lookup for a period of time).
– cdavid – 2017-10-04T19:24:22.787