Access to site before propagation

[rednose]

Hi

How does one have access to a site before propagation.

E.g
server I.P address 162.41.200.93
site is mysite.com

to see before propagation, I use

http://162.42.209.90/~mysite/mysite.com and I am just page not found. Where am I going wrong?

[LeeJ]

You are missing the ending "/"
example http://162.42.209.90/~mysite/mysite.com/

This is also explained the post below.
http://discuss.zervex.com/showthread.php?s=&threadid=42

[Andy]

What is the best way to access a frontpage web site before dns propagation?

I need to publish to the site as well and view it.

I really want to publish and test the site before moving dns.

Thanks for any help.

Andy

[LeeJ]

If the website has a non shared ip address you can use the ip address. If it does not you can add a subdomain alias via the Web manager interface.
The subdomain alias will need to be a top level domain that you have dns control over.

ex: yourclient.yourhostingcompany.com

[Andy]

I did what you say and it partially worked. I was able to publish and was prompted for password, but it published my files at the root directory and not under public_html?

Did I do something wrong?

Thanks

[Andy]

I'm not sure what you mean by subdomain that is a top level domain.

I do have another domain name that I control dns for.

How would I add this as a subdomain to my existing dsm account/domain? The subdomain option only allows a third level domain to be added such as test.mydomain.com

I tried adding a fp.mydomain.com but that did not work for publishing via http in fp client.

Thanks for your help.

Andy

[LeeJ]

add the domain to the account using the account manager. Be sure to link it to the primary domain name.

http://www.zervex.com/user_guides/html/Administrator/addingDomainToAccount.htm

[Andy]

Ok, I tried that but it still would not work. FP said it couldn't find root directory.

I'd like to know how to do this for the future, but I figured out a way to trick it by changing my local pc to use the web server's name servers for dns and then published -- it then had dns pointing to the new IP and host headers matched the site name.

Thanks