A network administrator is troubleshooting connectivity issues on a router filtering traffic between client workstations on subnet and an internal core server on host . Workstations are unable to resolve domain names using the internal DNS service hosted on . The administrator inspects the following IPv4 extended Access Control List (ACL) applied inbound on the workstation interface:
`10 permit tcp 172.16.20.0 0.0.0.255 host 10.10.1.5 eq 53`
`20 permit tcp 172.16.20.0 0.0.0.255 host 10.10.1.5 eq 88`
`30 permit tcp 172.16.20.0 0.0.0.255 host 10.10.1.5 eq 445`
Which of the following best explains why standard DNS queries sent by client workstations to the server are being dropped?
- Standard client DNS lookups primarily use UDP port 53, but rule 10 only permits TCP port 53, causing UDP queries to fall through to the implicit deny rule.Cevap
- BStandard client DNS lookups exclusively use TCP port 53, but stateless ACLs cannot inspect TCP headers without Port Address Translation (PAT) enabled.
- CDNS resolution services use destination port 5353 by default, making port 53 in rule 10 an incorrect port assignment for domain name resolution.
- DBecause an explicit deny rule was omitted after line 30, the router defaults to forwarding all traffic without evaluating lines 10 through 30.
Cevap
Standard client DNS lookups primarily use UDP port 53, but rule 10 only permits TCP port 53, causing UDP queries to fall through to the implicit deny rule.
Standard DNS client queries use UDP port 53 for fast, connectionless name lookups. Rule 10 specifies protocol `tcp`, which does not match UDP packets. Unmatched UDP DNS queries pass through lines 10, 20, and 30 without matching, hitting the ACL's mandatory implicit deny rule at the bottom and getting dropped.
Adım Adım Çözüm
Anahtar Kavram
Stateless ACL matching rules, transport layer protocol distinctions (TCP vs UDP for DNS), and the implicit deny behavior.
Tahmini Süre:2m 0s