Not expired folks. I just tried my link and it works fine. Maybe gremlins only hit certain computers???
This is most probably a Domain Name System (DNS) issue. Computers are identified by IP addresses, such as 72.32.121.187. Rather than enter a URL such as
http://72.32.121.187, though, we use names, such as (there was a url link here which no longer exists). DNS translates between the two, so when you enter (there was a url link here which no longer exists) in your browser, it contacts 72.32.121.187. (In fact, if you try entering
http://72.32.121.187 directly, it won't get you APUG, since HTTP, the Web protocol, embeds the name you entered in the request. This enables one computer to host more than one Web site, but it also means that entering the IP address directly often won't work.)
DNS uses a distributed database system -- many computers on the Internet host DNS records, and when you enter a hostname, your local DNS server (probably maintained by your ISP) caches the results for a period, so that it doesn't need to contact other DNS servers for subsequent lookups of the same address. This local cache typically lasts between a few minutes and a few days, so that sites can change IP addresses, when required. When you or another user of the same DNS server asks for the same address within the cache time, the DNS server retrieves the result from its local cache rather than perform a full DNS lookup. The result is that when changes are made to DNS -- such as when a Web site changes its physical hosting site, when a domain is first registered, or when a domain registration lapses -- the DNS changes don't appear simultaneously for all users. Local DNS servers cache old results for varying periods, depending on the last access of the hostname and DNS configuration settings.
What's happening here is that either your local DNS is still caching the old IP address (which is presumably still connected to the Internet), so your request is getting through to the original Photo Formulary computer; or the domain has already been renewed and your local DNS server didn't have the address in memory and so did a lookup on the just-renewed domain, but others' DNS servers are still working from the cache of what was returned by the domain registrar to the lapsed domain name. My guess is that the former would be more likely, since I'd expect the registrar to put a short DNS cache time on lapsed domains' lookups, but I've not checked this detail in this particular case.