What to do with the civicpdx.com DNS zone?

[MikeTheCanuck]

In 2017 we envisioned that civicpdx.org and civicpdx.com would be equivalent domains for all the future Hack Oregon projects.

However, the only resource that has ever been published in the civicpdx.com zone is http://service.civicpdx.com, which is currently an ALIAS record directing to dualstack.hacko-integration-658279555.us-west-2.elb.amazonaws.com. - which is itself just a load balancing resource (ALB) that sends requests to the "default" Target Group arn:aws:elasticloadbalancing:us-west-2:845828040396:targetgroup/default/23ff6ec307329848 - which sends requests to "/", which goes to ...

well, hell - where does that go to?

So now there's a few tasks:

• figure out what resource is actually answering to http://service.civicpdx.com - and if it's a duplicate resource to http://service.civicpdx.org, shut off the dupe
• remove the DNS "A" record for service.civicpdx.com
• decide whether to publish anything to answer requests for http://service.civicpdx.com, and find a home for that "page"