Resolve selective website loading failures across network devices

draft · network dnswebsite-loading

Generated by docuprocessor (prompt article/v3) · 2026-04-22 09:26

Source thread

thread_id: spaces/AAAA05BdS6s/threads/7QNLzyQMVBg · 3 msgs · first 2024-07-30 · participants: Tech ATech B

Tech A 2024-07-30 21:56

@all have an issue at CTIOF. the website marketgrader.com and interchangeably, app.marketgrader.com/login depending on which computer youre on will not load. On one of our computers they load no problem. On their server the .com loads fine but the app. does not load and on some computers there, neither will load. Dns on the server is set to loopback and 1.1 which is the unifi dream machine router which has 1.1.1.1 and 8.8.8.8 as its public dns servers, setting one of those public DNS manually on server or workstations doesn't help. Turning off content filtering on the router didnt help. Turning off country filtering didnt help. Rebooting the router didnt help. Any insights?

Tech B 2024-07-30 21:58

have you tried tracert to see where it dies out?

Tech A 2024-07-30 21:59

no, will do

---
title: "Resolve selective website loading failures across network devices"
category: network
tags: ["dns", "website-loading"]
source_thread_id: "spaces/AAAA05BdS6s/threads/7QNLzyQMVBg"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T09:26:20"
participants: ["Tech A", "Tech B"]
---

# Resolve selective website loading failures across network devices

## Problem
Multiple devices at a client office experienced inconsistent loading of marketgrader.com and app.marketgrader.com/login. One workstation loaded both sites normally, while the server could load the main domain but not the app subdomain, and some workstations could not load either site. The network used a UniFi Dream Machine router with DNS servers 1.1.1.1 and 8.8.8.8, and the server was configured with loopback and 1.1 (the router) as DNS servers.

## Resolution
1. Run `tracert marketgrader.com` and `tracert app.marketgrader.com` from affected devices to identify where the connection fails
2. Compare traceroute results between working and non-working devices to isolate the network path differences
3. Based on traceroute findings, adjust DNS settings or network routing as needed

Note: Initial troubleshooting attempts including manual public DNS configuration (1.1.1.1, 8.8.8.8), disabling content filtering, disabling country filtering, and router reboot did not resolve the issue.

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/7QNLzyQMVBg`

Generated article

draft