It does.
see the tcp video tutorials
The SYN packet, the SYN ACK packet , And ACK packet
denial of service
No it uses UDP packets.
3. syn, syn-ack, and ack. Then you're established.
UDP does not require as much resources as TCP but in the same time, it does not insure delivery of packets.
TCP does, not sure about others. TCP can handle out-of-order packets and lost packets. Even though TCP does some rudimentary error checking, corrupted packets sometimes get through.
Strictly speaking, the question is invalid, as DNS uses both UDP and TCP for its transport. The expected use is for DNS to run on top of UDP, with a fall-back to TCP for data packages that can't fit into a single 8K UDP packet. Large replies and zone transfers will fall in to this category. DNS can also be configured to work exclusively over TCP, but this isn't recommended. Early MS Windows systems used DNS over TCP exclusively. Fortunately the more recent editions (XP onwards) use DNS over UDP by default, falling back to TCP only when necessary. Why UDP rather than TCP? It's simply a matter of efficiency. To start a TCP connection a minimum of three packets are required (SYN out, SYN+ACK back, ACK out). By the time you add a data packet into that and close the session off correctly you will have sent several packets. In contrast, UDP can get away with a minimum of two packets (one question, one reply). DNSSec adds a layer of complexity to this, but with caching the extra resource required can usually be mitigated against a number of queries.
budotz2x
connect
TCP
TCP
In order to begin the handshake process, the client sends a SYN packet to the server. This is required to establish a synchronization with the server in order to ensure that both the client and the server will maintain and keep their exchange of packets in the right order. In order to complete the "handshake," the reponse from the server will be an ACK packet.