What does DNS primarily use to serve requests?

Study for the EC-Council Certified Ethical Hacker (CEH) v13 Exam. Utilize flashcards and multiple-choice questions with helpful hints and detailed explanations. Excel in your exam preparation!

Multiple Choice

What does DNS primarily use to serve requests?

Explanation:
DNS is built around small, fast request/response exchanges. For ordinary name-resolution queries, a client sends a compact request as a UDP datagram to port 53 on the DNS server. UDP is chosen because it has minimal overhead and provides low-latency delivery, which is ideal for frequent, tiny lookups. If a response would not fit in a single UDP packet or a reliable delivery is needed (for example, for larger transfers like zone transfers or DNSSEC-related data), the conversation can fall back to TCP on port 53. Other protocols like ICMP or HTTP on different ports aren’t used to serve standard DNS lookups, reinforcing that UDP on port 53 is the primary mechanism.

DNS is built around small, fast request/response exchanges. For ordinary name-resolution queries, a client sends a compact request as a UDP datagram to port 53 on the DNS server. UDP is chosen because it has minimal overhead and provides low-latency delivery, which is ideal for frequent, tiny lookups. If a response would not fit in a single UDP packet or a reliable delivery is needed (for example, for larger transfers like zone transfers or DNSSEC-related data), the conversation can fall back to TCP on port 53. Other protocols like ICMP or HTTP on different ports aren’t used to serve standard DNS lookups, reinforcing that UDP on port 53 is the primary mechanism.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy