Men&Mice Webinar Trilogy – Rethinking Name Resolution in Local Networks
Change always happens faster than we think. Quite a number of web developers may be caught off-guard when Google releases their new Chrome browser, which is intended to start enforcing TLS-encryption (HTTPS) for all domains ending in the top-level domain “dev”.
As the saying goes “all good things come in threes” so instead of just scratching the surface of this important development in one webinar, we’ve decided to go the whole hog and turn the discussion into a more detailed webinar trilogy on the subject of “name resolution in local networks.”
Part 1 looks at namespaces for local networks, Part 2 explores local name resolution in Windows networks and Part 3 concludes our local name resolution webinar trilogy by taking a deep look into local name resolution in Linux, FreeBSD and macOS/iOS.
Part 1 – Namespaces for Local Networks
Using a seemingly unused name from the Internet in a local network can be risky, as developers will soon find out once the new version of Google’s Chrome Browser starts shipping with the HTTP-Strict-Transport-Security Header enabled for the “dev” and “foo” top-level-domains.
In the first part of our webinar trilogy, we explore which domain names are safe to use in local networks. We have a look at the reserved domain names like “test”, the new domain “home.arpa” for the home-network-control-protocol and special domains such as “.local”. The webinar ends with a tutorial on how to host local names within the Unbound resolver, using special tricks such as “tags” and “views” to control who can “see” the local names.