(Solved): You are the network administrator for a mid-sized company. Recently, you needed to update the IP add ...

You are the network administrator for a mid-sized company. Recently, you needed to update the IP address for one of your critical web servers. You changed the resource record in your DNS server, but some users are still unable to reach the updated web server and are being directed to the old IP address. What is the most likely cause of this issue, and what should you do to resolve it? The DNS server is configured to use TCP port 53 instead of UDP port 53, causing delays in record updates. The DNS server is not authoritative for the zone and is providing non-authoritative answers. The TIL (Time to Live) value for the resource record was set too high before the change, causing cached records to persist. The zone transfer between primary and secondary DNS servers failed, causing inconsistencies.