Steps along the way with a webmaster that goes absent.

Throughout, the webmaster, N, was not able to be reached.

Power sits in two places

• The DNS server record has N as the OWNER, not Doug.
• Plus, the server is in N's control.

A fix will rectify both items.

Saga, step one:

Mark logged into the website with the username and password of the office manager. It was nice it was written down and in the office for Doug to read to Mark on the phone.  A back-up of the website was made by Mark. A few tiny changes were made to the site and new Administrators were put on the WordPress website including Mark, Doug and Brad. Meanwhile, the webmaster account of N was demoted to "author" -- not administrator. Also, a SwimISCA.org backup obtained by Mark was replicated at Mark's server, https://Op-Ed.CLOH.org.

Step two:

N used a back-up of website and replaced the above changes which also returned N to the administrator status.

Step three:

Using the older log-in again, Doug, Brad and Mark were put in again to administrator status, but this time, N's account remained as an administrator too.

Step four:

Some additional changes were made to the website, moving coach advisors and scienc advisors to their own pages and removing some dead-end items in the main menu.

Step five:

The owner of the DNS was discovered to be N, as expected. The desired change to the DNS records were requested, in part, because we wanted to launch a new blog site, blog.SwimISCA.org. Nate did make a new domain, blog, but didn't do the name switching.

Step six or so:

The AWS new domain, Blog.swimISCA.org is linked to all the themes and plug-ins of the main site, wrongly. Wanted: A new and different domain that is independent of the main site. Then this alert comes too about disk space limits.

Conversation from Mark to Kerrie @ Nate's call on April 10, 2020

1) Doug to be the OWNER for DNS for SwimISCA.org 2) Turn off the whoisprivacyservice.org so the DNS records are visibl 3) Set the TECH contact for the DNS for SwimISCA.org to Mark@Rauterkus.com. 4) Set up with AWS (Amazon Web Services) an IAM account as part of the SwimISCA account, for Mark@Rauterkus.com. 5. What FIXED costs are for the web services and software with a full audit with software, costs, expiration of license, etc.Woo Subscription Services, for instance. $, due again? 6. If you want to hook me in on a 3 way conversation, I'm happy to do so.

Reply:

Yes. He's (Nate) putting together all the information and will provide it to me (K) in the next couple of days. He's (N) available to assist on a minimal basis during the transition. He (N) is still working full time, but he will try to answer any questions we have moving forward. I (K) will let you (Mark) know when I get it all.

Mark Rauterkus to ISCA

Great. Good news I guess. So Nate is going to put Doug in as the DNS Owner?And, is Nate going to get rid of himself in the future?For now the web site is trash. I guess I will just sit idle on the web site and work on other things and not worry about the web pages on his server???

The long and winding road, April 11. No websites at blog.swimISCA nor swimISCA.org

Doug called: Nate will furnish him with all the needed bits by Monday, April 13. Nate will fix the website to its former self, we hope. I'll stay away.

Possible next move could be...

I (Mark) was going to migrate the  ISCA extra web site, https://ISCA.CLOH.org, onto SwimISCA.org, as a place holder with a message of a re-build is underway. However, I can't even do that as the SwimISCA.org site is with a database error now. If I get access to WordPress again at SwimISCA, I'll do some quick fix.

Can't get any support from AWS

With my account on AWS (Amazon Web Services), I can't even send in a support email. There are plenty of documents, but no place to deliver any support requests.

Easter Rebirth with a backup of the main site

The main website https://SwimISCA.org, is up again, as of Easter morning, April 12. N installed a backup. The minor changes made in the past couple of weeks are not present. FWIW, the administrator accounts are not present.

"Who is," no movement yet.

The only thing to watch now is the DNS record. When this changes, things can move forward. The update date reads September 25, 2019.

Domain Name: swimisca.orgRegistry Domain ID: D402200000003796055-LRORRegistrar WHOIS Server: whois.registrar.amazon.comRegistrar URL: https://registrar.amazon.comUpdated Date: 2019-09-25T15:37:33.490ZCreation Date: 2017-10-02T18:58:43Z

WHOIS insights

WHOIS is the system for looking up information about domains. WHOIS look-ups show the status of the domain, and other details such as its creation date, expiration date, and the date the domain was last modified as well as the name servers. DNS = Domain Name Servers. Contact information for the Registrant (Owner)Contact information for the Administrative, Technical, and Billing ContactsNote: The Billing Contact is not currently shown in WHOIS for .COM, .NET, .ORG, .MOBI, and .ME domains.

Got access

Using Kerrie's log-in info, I took a 3+ hour tour of AWS on Thursday night.

Go figure, SwimISCA.com and SwimISCA.org are there, but only one is used!

The domain contact was not moved yet. Here are the DNS records and snapshot. The only big thing I did was un-mask the cloaking of the record so we'll all be able to see who owns the record(s). In the AM, I'll get the okay to make the changes with a call or text to Doug & Kerrie.

Does this make sense to you?

• https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-inactive.html