[VAXman(Admin)]

A little "techie" for those of you interested in what is happening here.

The new server is up and running. Its IP address is 64.253.47.118.

In order to get to the new server when you use auralmoon.com, your machine must query the internet Domain Name Servers (DNS) to get the IP address of auralmoon.com.

For each domain, there are typically a minimum of two DNS (known as primary and secondary) defined to resolve a domain name to its IP address. The old site had listed ns1.auralmoon.com and ns1.halibut.com. ns1.auralmoon.com is the auralmoon server itself and ns1.halibut.com is some service which Dr. • got to host auralmoon's nameserver info for a secondary.

The new server has its DNS info listing ns1.auralmoon.com and ns2.auralmoon.com. ns2.* is somewhere in Tampa Florida AFAICT.

The information as to which nameservers are to be used to resolve a domain are located with the registrar. If you have access to "whois", you can issue a "whois auralmoon.com" and see this information for yourself. This information should have been updated to list ns1&ns2 .auralmoon.com. This is not the case. ns1.halibut.com is still listed as a nameserver for auralmoon. ns1.halibut.com is ALSO still advertising the OLD server information.

You can "dig @64.253.47.118 auralmoon.com" (ns1.auralmoon.com) and "dig @66.232.101.2 auralmoon.com" (ns2.auralmoon.com) and see that the DNS info is correct. However, if you "dig @ns1.halibut.com auralmmoon.com" you will see the old info.

Until the registrar has the correct domain information in its databases, this is going to be a problem.

Avian sent me an email with the registrar information and the password. I tried to change the information but it refuses to change. This registrar if on west coast US time. When they are open later today, I will call their support and seek their assistance in getting this mess resolved.

This is not a hardware issue. The new server is UP and RUNNING (save for a several (5) hour power outage Tuesday evening which drained my UPS), it has been up and running. There are instructions here within this discussion thread to add auralmoon.com to your machine's hosts tables. These will override the IP definitions sought by your machine of these faulty DNS. You can safely add this address, I doubt it is going to change as I own the IP block -- as long as I keep paying for it, that is.