PDA

View Full Version : domain ip forwarding problems



forcer
July 27th, 2003, 16:26
this is the only suitable forum to post, i did contact my hosting company but the guy must be on vacation or something because he usually offers instant support but hasnt replied for about a week.

ok so my domain is www.digitalbreeze.net

the namesevers for this domain are @ www.mydomain.com because this is where i manage my domain as i have 2 servers.

the main domain www.digitalbreeze.net points to my main server using ip pointing.

i created a subdomain on the mydomain.com control panel to link to http://2.digitalbreeze.net

for some reason i got the IP's messed and now instead of going to my site main page it takes me to that apache is successfully installed page.

which can be accessed here...

http://cpanel2.rtpsearch.net/

and if u put ~forcer on the end for acount name it goes to my main page.

http://cpanel2.rtpsearch.net/~forcer/

i want www.digitalbreeze.net to link to http://cpanel2.rtpsearch.net/~forcer/

but through IP forwarding. the IP is :: 216.67.228.47

but when i forward it to that IP it goes to the main apache page instead of my home page.

can any1 offer me asny help. thanx

NukedWeb
July 28th, 2003, 20:21
Looks like a config problem from the webhost. It's most likely that they use virtual hosting for their service, to use more than one domain on one IP. When your browser connects, it sends a header like "Host: www.digitalbreeze.net", so the server knows where to send the visitor.

The only one that could fix that is the admin. Might wanna try a phone number if ya have one. =)

Dominan
July 29th, 2003, 08:07
The only way for the end result to beaccomplished is for you to url redirect the domain name to the site you require. Otherwise change the nameservers of the domain to your host account nameservers.
Probably the reason why you have not had a reply from your host is because the domain is residing on third party servers. The domain has been setup to be authorative on the host nameservers and is expected for the domain to reside on these servers.
This is a classical example of people managing the dns of a domain, whom do not know how dns works.

forcer
July 29th, 2003, 08:11
how come it worked fine before.

i simply set up www.digitalbreeze.net to link to the domain on my account and it worked fine.

is it possible to use ip forwarding on a cpanel account to make a domain go to a different server?

Dominan
July 29th, 2003, 08:27
If the domain resided on the authorative nameservers you would not have probably experienced this latest problem. All sites have 2 nameservers which is required under ICANN rules and these nameservers are provided by the hosting company. There is no need to involve a third party dns hosting company to provide dns for your domain.
By having the domain at the third party provider, the hosting company cannot be responsible for any problems that occur.
Maybe it did work before, in some cases, this happens, but dns tends to work it self out and then you get where you are now.
If I was the hosting company, your domain would have been placed on the servers otherwise you would not have continued with the account.
As I said previously a classical example of ignorant mismanagement of a domain's dns.

forcer
July 29th, 2003, 08:39
i'm not sure you understand. my name servers for the domain point to mydomain.com which is a perfectly normal thing to do and yes i have reasons for hosting my domain here and what i done with the ip pointing is a normal option which did work and still works on my 2.digitalbreeze.net subdomain but not on my main domain anymore.

Loon
July 29th, 2003, 10:09
I think the reason it doesn't work is because you or your host have not setup an account for the subdomain.

Unless you have a dedicated IP, if you're a reseller for example, any domains that you point to that main IP wont automaticly resolve to your website, because it's not your IP, it's shared with every account on the server, that's why you get the apache page.

If you have the option to setup subdomains from your control panel that's what you need to do, so the account is the "looking" for the domain, if you don't have that option you need to get your host to do it.

Are you paying for this host that's "gone on holiday" :confused2 and why does he not have his own nameservers?