New Website

[MrMagoo]

For those having domain problems on Windows boxen:

1) print out or email these instructions to yourself
2) quit all browsers
3) open Notepad (Start -> All Programs -> Accesories -> Notepad)
4) File -> Open... (Ctrl+O)
5) change 'Files of Type' pull-down at bottom of Open dialog window to 'All Files'
6) click 'My Computer' on left pane (or your computer's name)
7) double click 'Local Disk (C:)' in center pane (or your system drive's name)
8) double click 'Windows' folder in center pane
9) double click 'system32' folder in center pane
10) double click 'drivers' folder in center pane
11) double click 'etc' folder in center pane
12) double click 'hosts' file in center pane
13) the file should look like (between the ===== lines):

=====
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost
=====

14) add the following 2 lines at the bottom of the hosts file (note the space(s) or tab between the IP address and the name):

64.253.47.118 auralmoon.com
64.253.47.118 www.auralmoon.com

15) File -> Save (Ctrl+S)
16) restart your browser

The above instructions are for WinXP Home, here's where the host file is located for other flavors:

Win95/98 hosts file location:
Windows 95/98/Me c:\windows\hosts

Win2k hosts file location:
Windows NT/2000/XP Pro c:\winnt\system32\drivers\etc\hosts

Xp hosts file location :
Windows XP Home c:\windows\system32\drivers\etc\hosts

[Rick and Roll]

Originally Posted by MrMagoo

[noparse]
For those having domain problems on Windows boxen:

Magoo you are the MAN. I'm in at home and work

[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.

[Rick and Roll]

I actually followed that. This is getting scary.

[VAXman(Admin)]

Originally Posted by Rick and Roll

I actually followed that. This is getting scary.

ROTFLMAO!

Thanks Rick, I tried to simplify the issue for all to understand.

I couldn't follow the registrar change forms on the web site; therefore, I called the customer support assistance. Seems I was going about the change request the wrong way. This registrar needs to change a few things about their web site, IMHO.

Anyway, I now have the new IP addresses registered with them as nameservers and that then permitted me to be able to update the nameservers for the auralmoon.com domain. When this information propagates, things should clear up. The usual time from zone change to propagation is about 24 hours; however, the registrar's site says it can take as much as 72 hours. I've never seen it take that long.

I was out last evening and accessing the internet from a restaurant using my Sprint EVDO card. The Sprint nameservers still had the old zone info. I will use Sprint's nameservers as my testbed to see if/when this new zone info propagates.

[Rick and Roll]

I went to request a song and it denied it, saying when it last played and when it can be played next.

THAT IS A DAMN COOL FEATURE!

[MrMagoo]

Found a picky music search bug: 'Friday' in 'songs' = 10 results, same in 'artist' = 0, same in 'album' = 5, but same in 'All' = 0?

[Wizzzard]

[quote=MrMagoo][noparse]
For those having domain problems on Windows boxen:


Thanks a lot, it worked!!!