DNS Negative Caching Checklist for School Recognition Display Content Changes
When a school changes the hostname that delivers recognition display content — migrating to a new content platform, correcting a subdomain, restructuring a district DNS zone, or switching from one cloud endpoint to another — every DNS resolver on the path between the kiosk and the internet may have already cached a negative answer for that hostname. A negative DNS answer, called an NXDOMAIN response (Name Non-Existent), tells the querying resolver that the hostname does not exist. Under RFC 2308, resolvers cache that negative response for a duration set by the zone’s SOA record. Until that negative cache entry expires — or is explicitly flushed — any kiosk, content player, or browser on the school network that queries the new hostname receives NXDOMAIN from cache rather than performing a fresh lookup against authoritative DNS.
Read More
Split-Horizon DNS Checklist for School Recognition Display Content
A school’s lobby recognition display, athletic hall-of-fame kiosk, or hallway honor wall connects to a content platform over the school’s network. That connection starts with a DNS lookup: the display’s browser or application resolves the recognition platform’s hostname into an IP address before it can fetch athlete profiles, inductee records, award rosters, or media files. In most schools, that lookup travels from the kiosk to the school’s managed DNS resolver, then to the internet, and returns a public IP address — the same address anyone outside the school would get. That works for platforms that serve all clients from a single public endpoint.
Read More
