After a cutover, citizens cannot resolve the municipal portal hostname even though the application servers respond when reached by IP. What should the operations team investigate first?
Select an answer to reveal the explanation.
Short Explanation
If you can hit the portal by typing an IP but names bounce, the app is probably fine—DNS is the map that went missing. Check the hostname records and whether the new zone has actually spread yet.
Full Explanation
Name resolution failures after cutover commonly stem from incorrect A/AAAA/CNAME records, wrong hosted zone, TTL/propagation delay, or clients still caching old answers. Reachability by IP isolates the fault to DNS rather than compute or application code. Patch levels, object lifecycle, and disk IOPS do not explain hostname resolution failures.