| 4. |
dig example.com returns 192.0.2.10, but dig -x 192.0.2.10 returns a completely different host name. Why is this not necessarily a misconfiguration?
Please select the best answer.
|
| |
A.
|
The reverse lookup failed and returned an unrelated cached record |
| |
B.
|
Forward and reverse records live in separate zones under separate administrative control, and nothing in DNS requires them to agree |
| |
C.
|
The -x option does not perform a real DNS query |
| |
D.
|
A PTR record must always match its A record, so the zone is broken |