DNS translates a service name into the information needed to reach it. A lookup problem may affect one website, an internal application, or many services. It does not automatically mean the website server is down.
Identify the failing name
Record the full hostname and the exact browser or application error. Compare the same name on another managed device. If policy permits, compare access using a separate internet connection without signing into sensitive business services on an untrusted network.
In Windows Command Prompt, this read-only lookup checks the example name using the device's configured resolver:
nslookup example.comReplace the example with the affected hostname. Note the responding DNS server and whether you receive an answer, a timeout, or a name-not-found result. A lookup answer is evidence of resolution, not proof that the website itself works.
Preserve business DNS settings
Do not replace a company DNS server with a public resolver as a general fix. Internal domains, directory services, VPN resources, and security filtering may depend on the managed configuration. Flushing a local cache also does not clear an ISP's or another upstream resolver's cache.
Send the evidence to support
Include the hostname, timestamp, resolver shown, affected connections, and recent domain or network changes. Your administrator can compare authoritative records, cached answers, and filtering policies. If a security product blocks the name, request a classification review rather than disabling protection.
Get help with your network
For an existing service issue, open an AvrinTech support ticket. For an assessment or planned improvement, request a scoped proposal and review our networking services. Work, coverage, and response targets depend on your agreement.
