CyberCertPrepNetwork FundamentalsDNS & DHCPEASYFree question
Scenario
A network engineer runs a traceroute and DNS lookup during troubleshooting. The 'nslookup' command shows that the DNS server at 192.168.1.1 is responding with the correct IP for external websites. However, internal hostnames like 'fileserver.corp.local' do not resolve.
What DNS architecture issue is most likely causing internal hostname resolution failure, and what is the correct fix?
- A.The internal DNS server is down; configure a secondary internal DNS server to resolve the issue
- B.The '.local' TLD is blocked by the ISP's DNS resolver as a security precaution; use '.internal' or '.corp' instead; root hints are downloaded from the TLD servers each time the resolver restarts. TTL zero on a DNS record instructs resolvers to cache it indefinitely. NS records store the IP addresses of a zone's mail exchangers. Hosts renew leases by contacting any DHCP server, not the one that issued the lease, as the protocol keeps no server identity
- C.The DNS server at 192.168.1.1 (likely the home router/ISP resolver) does not have the internal 'corp.local' zone; it can only resolve public internet hostnames. Fix: configure workstations to use the internal DNS server (corporate AD DNS or Windows DNS with the corp.local zone) as their primary DNS, not the router/ISP resolver. The internal DNS should forward external queries to the ISP resolver