new account temp URL

Greetings,

I am having some difficulty understanding why my account is responding the way it is (difficulty most likely due to lack of knowledge).

PSUEDO names used:
Domain: Domain.com
Server - 123.123.123.123
Server IP is set to Server, not shared

User accounts setup:
Domain: User.com
AccountName: user
Server - 123.123.123.555

Server IP is set to shared

New domain name is not in effect yet. User wants to be able to access site through temp URL.

TEST 1
Load URL http://domain.com/~user
Result - HTTP 404 File not found error

TEST 2
Load URL http://123.123.123.123/~user
Result - Account is found and pages are loaded

TEST 3
Load URL http://123.123.123.555/~user
Result - HTTP 404 File not found error

-------------------
I thought the account should be accessible by using test1 or test3. The domain (user) is setup in DA to use the 555 ip address.
The only other thing I can think of is the DNS which is using:
ns1.domain.com -> 123.123.123.123
ns2.domain.com -> 123.123.123.555

Since I don't know, I am asking for some help....can anyone help me know if this is normal and if not, what to do to fix it?

When modifing a user:

Change the User's IP

Set IP To : Select box of available IP shared/not shared

This should be set to the .555 IP.


-------

Admin:

IP Management:

The ip can be assigned to a specific reseller so it is available

-------

DNS Management:

You can change the domain.com A [ip 555]
And other A records that need to be affected

---


These are 3 options to set the IP.

thanks for the reply.

our user is set as described

ip management is set to reseller as described

DNS Management:
for Domain.com, should we add an A record for 555 to be included in the list which already has 123 listed?
Also, we only have one PTR which is set to 123. Do we need 555 also?

thanks~!

We'll if the DNS is set to 123 than you probaly specified somewhere that it should use 123!

You could remove the old ones and add the new ones

you are correct that we did specify that .123 was to be used by our primary domain which this IP address will be used for SSL purposes. The 555 IP is for all other shared accounts.

I find using

http://xx.xx.xx.xx/~user

to access a site temporarily to be very ineffective.

Any cgi script will fail because of suexec, server variables (Document_root etc) also go haywire.

I've found 2 ways round.

1/ If it's just for me while I develop the site, I put an entry in my local hosts file so that I can use the normal domain name

2/ If I want to demonstrate to someone else (eg a client!) I use another temporary address: I keep a special domain name for this purpose. Let's say its 'demo.com'. The DNS for demo.com accepts any subdomains and points to the server IP. So newdomain.demo.com is already pointing at the server. To make it work for the account in question (newdomain.com), I add a new domain for the user making newdomain.demo.com the new domain name.
I then delete the folder for newdomain.demo.com and replace it with a symbolic link to the newdomain.com folder.

It may sound complicated, but its actually quite straightforward.

I'm actually thinking of creating a create_domain_post.sh script to automatically handle the delete folder/create symbolic link if the new domain name includes '.demo.com'.

Done this way the temporary address is fully functional immediately.

I recently posted a similar method that doesn't require using shell access...

I create a new DNS entry under that "special" domain (because we have multiple IP#s your wildcard method won't really work for the way I do it, though it will for yours), then as admin, I add a ServerAlias directive to the site's httpd.conf file.

From my point of view the advantages are:

I don't have to log in as shell.

I don't have created site sitting around to remember to delete.

Jeff

Jeff

Point taken. I think your ServerAlias is a great way round it.

Mike

Further to your idea, I have now created a custom virtual_host.conf template that includes |USER|.demo.com at the end of the Server Alias line (where demo.com is my test domain name - always pointing at the correct IP address).

Now the test address automatically works on creation of the site.
(And there is no need to delete it!)

Thanks Jeff!

Mike