The "non-conspiracy, Occam's Razor" Scenarios:
Neither one of the listed nameservers for the FRN's current/cached whois listing appears to be "answering" queries.
This may be that those physical servers are offline and web queries to Joplin.com/JoplinGlobe.com are being forwarded; however since the Joplin Globe is now mirrored elsewhere, there may be no serious imperative to do much about the former hosting server FRN, or other non-essential sites.
Somehow, while it appears that Joplin Globe was reliably mirrored elsewhere, that the FRN did not receive the same courtesy.
Cached Google records (from when FRN was UP) point to the current server where 74.84.203.168 and 69.38.106.211 -- these appear to be proper mirrored servers for Joplin Globe. For whatever reason, perhaps the FRN didn't survive the move or doesn't have a solid hosting agreement with the current hosts of JoplinOnline.com or the newspaper group they're now part of. While I'm to Understand John Cruzan still works for the Joplin Globe group, they just don't seem to be sharing server space with them at present.
GeoIP Tools imply that the server for the Joplin Globe is now actually hosted or at least registered nowhere near Joplin (in light of recent tornado events this is a recommended strategy, why the FRN wasn't mirrored accordingly is unknown):
Host Name: nsc69.38.106-211.newsouth.net
IP Address: 69.38.106.211
Country: United States
Country code: US (USA)
Region: South Carolina
City: Greenville
Postal code: 29615
Calling code: +1
Longitude: -82.2464
Latitude: 34.8601
AND:
Host Name: 203-168.baymountain.com
IP Address: 74.84.203.168
Country: United States
Country code: US (USA)
Region: Virginia
City: Fredericksburg
Postal code: 22401
Calling code: +1
Longitude: -77.4826
Latitude: 38.2981
Long and short of it appears to be that FRN.net has lost its home on the interwebs. If it were a simple backend database failure, you'd still get error pages when looking up FRN. Or an administrator chose to pull it down without putting any placeholder messages in its stead.
If intentional, this is kind of unusual practice, as it causes worldwide DNS caches to drop all records of FRN; at present only domain ownership records remain current.
One other possibility exists: *.net domains are painfully tricky to move or transfer hosts; I learned this when attempting to move my own site, corqspy.org. Ideally you move a copy of your files to the new host, leaving the old files in place on the old server,until the forwarding kicks in - in my case it took over a week and a half.
When the domain forwarding from one host to the other finally kicks in, hopefully your files are already present on the new server - and no one's the wiser.
I suspect a hosting change might be the root of all this, and that as soon as the new home of the FRN pushes out its ip to worldwide DNS servers, life will resume as normal.
Normal, of course, being a relative term.