The reason that I reported that the URL didn’t work was because the “dot” in “dot com” was missing in the original link. Good discussion though.
Craig KE7MPM
From: PSDR <psdr-bounces@hamwan.org> On Behalf Of Jeff Francis™
Sent: Saturday, November 24, 2018 3:09 PM
To: Puget Sound Data Ring <psdr@hamwan.org>
Subject: Re: [HamWAN PSDR] Radio World: Cause of Tiger Mountain Fire Disclosed
It's not a router limitation, it's a matter of the website owner making the effort to make sure that his webserver responds to www.domainname.com and domainname.com in the same way (because by default, they do not, which is correct behavior because these are two completely different domain names). Typically, the hosting company will create a DNS A record for domainname.com, then a CNAME record that points to the previous A record for www.domainname.com (though there are certainly many variations on that theme, depending on how your servers are configured). Then you just configure Apache/IIS/whatever to respond to both domain names with the same content. It's not a router issue, it's a laziness/awareness issue. And enough people don't make the effort to get this right that it's always worth checking for the behavior you expect before passing along a truncated DNS name (ie, without the leading "www") and leading people to links that don't work.
Jeff/N0GQ
On Thu, Nov 22, 2018 at 7:59 PM Tony Ross <w7efs@centurylink.net> wrote: