Hopefully your host can keep your existing account username. As long as the domain remains the same, it shouldn't be a problem for you.

Thanks for the response bobbymac,

here is the response I got from MD:

You can go ahead in changing the primary domain for your hosting account from 'growinold.com' to 'christsknights.org'.
To change the Primary Domain of the Hosting Account, an administration fee of $22.00 applies. The changes will take approximately 30 minutes to complete. We will first change the primary domain name on our servers which will reflected once the customer login to the control panel. We will then update our billing systems which reflect on the hosting package details.
Please conform us and reply back to proceed further on this process.

Jessy
support@mdwebhosting.com.au
MD Web Hosting

What questions do you suggest I ask them to ensure everything stays functional?

I would have thought that paths to uploaded files etc would be an issue etc? O
nce I change the primary domain name won't "growinold/public_html/christsknights.org" become "christsknights.org/public_html"? thus affecting all of the data uploaded into the subdirectories there?

What questions do you suggest I ask them to ensure everything stays functional?

I would have thought that paths to uploaded files etc would be an issue etc? O
nce I change the primary domain name won't "growinold/public_html/christsknights.org" become "christsknights.org/public_html"? thus affecting all of the data uploaded into the subdirectories there?

Hey Jup,

It depends completely on the server configuration, but it looks like the "growinold" bit there isn't necessarily a reference to your domain, but is rather your [strong]username[/strong] on the linux box. Do you know the absolute path where your data is stored? It's probably something like "/home/growinold/" or so... At any rate, what has probably been done is two directories have been set up:

growinold/public_html
growinold/christsknights.org/public_html

In the "growinold/public_html/" directory, there is most likely a symbolic link pointing to the "growinold/christsknights.org/public_html/" directory. That's just my guess... Do you have shell (ssh) access to the account? If so, you could log in and do:

# cd
# pwd
# ls -la

(Those are three separate commands, each one at a command prompt indicated by the pound sign #).

For example, on my local machine, when I do that, here is the output (I'm cheating some of the directory outputs because this machine is only hosting stuff locally, not publicly, but you'll get the idea):

You can see, after the first command is run, the prompt changes from "dhcp-10-71-7-161:/" to "dhcp-10-71-7-161:~". That indicates that I'm no longer at the server's root (/) but am now in my home directory (which is indicated by the ~ but is the exact same thing as /Users/luke). The next command--"pwd"--stands for "print working directory". It'll tell you where your home directory is located on the server. The next command "ls -la" (those are lower case "L" by the way) lists all files and directories (along with their associated permissions and whatnot). That will list for you everything you have in your home file--then you can just start poking around to see where stuff is stored.

It's important to have a good sense of how your host has structured their server, and really the only way to do that is to start poking around and see where things are kept. If you're going to be doing a lot of hosting on Linux/Unix based systems, I highly recommend the book "Linux Pocket Guide" by Barrett at O'Reilly Press /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

What they are changing when they apply that $22 fee is most likely just a paperwork thing.

Hope this gives you a launching point to start poking around and breaking stuff!

God bless,
Luke