Here is a second article of a series covering some important aspects about the DNS protocol to troubleshoot applications performance issues.
For various reasons (size of database, performance, redundancy, security), when trying to translate a FQDN (Fully Qualified Domain Name) into an IP address, a single DNS server cannot answer all requests by itself. To do that on his own, it would have to store all FQDNs defined worldwide and be able to handle all requests !
This is the fourth article in the article series covering TCP core concepts to effectively troubleshoot performance problems impacting applications.
After considering how the TCP retransmission mechanism works , we will now examine TCP Receive Windows and how they can impact performance.
This is the third article of this TCP series, covering all you need to know to troubleshoot performance problems impacting business critical applications.
Here is a first article of a series covering some important aspects to know about the DNS protocol when troubleshooting applications performance issues.
First of all, let’s have a look at the DNS protocol itself.
TCP Series #2: TCP Closing a SESSION
Here is a second article of a series covering all you need to know to troubleshoot performance issues impacting applications relying on the TCP Protocol.
After studying how TCP sessions are established we will now see what can go wrong when closing a TCP sessions.
Do you know that?
- "93% of the organizations are wasting piles of money on unused or underused application software, otherwise known as « shelfware ».
- "20% of the organizations reported a loss over 1m$." (source: Flexera)