Why the main page can work while other files fail

A web page is rarely a single file. After your browser receives the page, it may request stylesheets, images, fonts, and scripts from other addresses. Some of those files may use a hostname different from the one in the address bar. For example, a page at www.example.com might load an image from images.example.com and a stylesheet from assets.example.com. Each hostname needs its own working path to the file.

This makes a partly loaded page a useful clue. Readable text with no styling, blank image spaces, or controls that do nothing can mean that supporting files failed to load. It does not, by itself, prove a DNS problem. The files might be missing, blocked by the browser, rejected by the server, or affected by a certificate error. The first task is to identify which requests failed and what error the browser reports.

Find the hostname behind a failed file

Open the affected page in your browser’s developer tools and look at the Network panel. Reload the page so the panel captures its requests, then find a failed image, stylesheet, font, or script. Note the request’s hostname and its reported status or error. You do not need to share the full request URL: its path or query string could contain information you would rather keep private.

Compare the failed file’s hostname with the hostname of the page itself. If several failures all use one separate hostname, investigate that hostname first. A message indicating that the name could not be resolved points toward DNS. An HTTP response, such as a 404, means the browser reached a server and received a response, so checking the file location or server configuration is usually more productive. Certificate warnings, blocked mixed content, and browser policy errors also call for different fixes.

Check whether the asset hostname resolves

Run a DNS lookup for the failing hostname using a tool such as nslookup or dig. Enter the hostname, not the entire URL. Compare its answer with a lookup for the page’s hostname, but do not expect them to have the same IP address. Sites commonly place supporting files on different services. What matters initially is whether the failing name returns a usable answer or an error.

If the asset hostname has a CNAME record, follow its target to see whether that name resolves too. If you manage the domain, check that the asset record exists in the active DNS zone and that its target is spelled correctly. A record present in an old or inactive zone will not help browsers using the domain’s current nameservers. If you recently changed the record, compare answers from the resolver your device uses and, where appropriate, the domain’s authoritative nameservers. Cached answers can temporarily differ.

A successful lookup does not establish that the file will load. It only narrows the question: the browser has an address to try. If DNS succeeds but the request still fails, return to the browser’s error and check the connection, certificate, or server response rather than repeatedly editing DNS.

Compare failures without changing too much at once

Check whether the same files fail in another browser or on another network. If one browser fails while another works on the same device, an extension, browser setting, or cached browser data may be involved. If devices on one network fail but another network works, compare the DNS answers they receive before changing records. A difference is a clue, not automatic proof that either answer is wrong.

If you control the website, make one targeted correction at a time and reload the page while watching the same failed request. Record which hostname, DNS answer, and browser error changed. Avoid replacing records for the main website merely because an asset hostname is failing; the working page and the broken file may depend on different records. By following the individual request from its hostname to its DNS answer and then to its browser error, you can keep a partial page-load problem small enough to diagnose.

Back to category ↗