Web Hosting Talk







View Full Version : Please help guys - http://209.51.159.130/~whatever-works/


ceo
07-16-2002, 03:18 PM
This works at earhost.
http://209.51.159.130/~whatever-works/
But the domain name whatever.com does not.
It goes to a default page saying "default page"
The DNS is fine therefore !

Can you please tell me what must be done in the WHHM to check well if the DNS service there is proper ?
Any other clues ???

esdjco
07-16-2002, 03:29 PM
ceo...:eek:

Eh? Why not just contact james at earhost.com and ask him.

Chaps
07-16-2002, 03:53 PM
hehe...i think the answer to that is that you'll never get an answer from earhost.........
:D

ceo
07-16-2002, 03:55 PM
Eh... You must know that getting replies from him/support are as tough as counting half the stars in the sky, right now....

; )

Just thought some good soul knowing this would help here !

Alan - Vox
07-16-2002, 04:22 PM
Its something that needs to be sorted by the server admin.

Website Rob
07-16-2002, 04:44 PM
Good information allows for good answers.

Is the Domain Name still propagating?
Is IP Shared or Dedicated?
Is "whatever.com" just an example, it redirects to funny.com which works fine.
Did you get a "Welcome" Email with account login details?
What "exactly" is the problem?

ceo
07-16-2002, 04:56 PM
Is the Domain Name still propagating?
==Domain Name reaches the server with a page "default page"
I thus assume it's propagated....

Is IP Shared or Dedicated?
==I'm pretty sure it's shared.

Is "whatever.com" just an example, it redirects to funny.com which works fine.
== An EXAMPLE only

Did you get a "Welcome" Email with account login details?
== No.

What "exactly" is the problem?
== The problem is that I do not know how to make sure the site say 'abc.com' works.
- The domain has the right DNS & it's propogated well.
- The domain reaches some place on the server with a general "default page" message
- The actual path as given by another earhost client works correctly ie - http://209.51.159.130/~abc/
- Now I need abc.com to go here isn't it ?

So what exactly must I do in WHM to see it's successful.
I created an account & it adds up the DNS details.
If I try to edit DNS it's too complicated so I leave it.
So anyting you can help with ?

Thanks again !
And if you want it more clear, I'll leave my actual domain name !

Website Rob
07-16-2002, 05:15 PM
What "exactly" is the problem?
== The problem is that I do not know how to make sure the site say 'abc.com' works.
Call me dumb, but I still don't understand what the problem is?

Are you perhaps, referring to the default page shown when a new account is setup?

ceo
07-16-2002, 05:27 PM
I'll go nuts now.

So please go to : http://209.51.159.130/~sst/
That works right ?

Now go to : http://www.simonsaystraffic.com
Why is the name NOT being directed correctly ?

Is it my error, the admin's error or .... ?
Let me know please.....

Choppy
07-16-2002, 05:49 PM
The Server admin must take a look at it chances are that he did not enter the right information when building the account thuse even though you are pointing to the right server it doest actually know were to send your domain to!

I hope that make sense!

e.g if you type abc.com and the link is http://1.1.1.23.2/~abc/

If the server admin has not related the Domain name with your username being abc it will not work. I would think though it would just come up with an error!

Not sure past this point like everyone if i had access to the server i would be able to help out more.

Kind regards

Website Rob
07-16-2002, 05:50 PM
Because they are pointing to different IP's.

209.51.159.130
http://209.51.159.130/~sst/

209.51.159.221
http://www.simonsaystraffic.com/

Being as http://www.simonsaystraffic.com/ is being re-routed by NS3.ELITE-DNS.COM and http://209.51.159.130/~sst/ is using a shared IP address, you will probably have to change your account settings at ELITE-DNS.COM to reflect that a Shared IP is being used.

Something is odd here though. The ~sst URL looks like a login URL for an account with a shared IP yet, simonsaystraffic.com has it's own IP address and shouldn't require the other URL -- for account access that is.

You know better than I, what is going with these URL's and until they are pointing to the same IP address, your problem will not go away. The problem is not with WHM, it is with your Registrar.

Does that help?

ceo
07-16-2002, 06:16 PM
Thanks.

Well it's rare you say the Domain Name's pointing to another IP ?
Well I've not checked that, and all you said made some sense yes, but what's my resolution ?

1. Should I tell James to just resolve the problem (whatever it is)
2. Change something at the Registrar end (which is not IMHO required as Enom taked IP after entering NS automatically)

Unfortunately (1.) I've already done.
But nothing happening there.
So now that you tell me there's nothing in WHM that I can/must do..... I'll just need to wait for James to help me here.......

Thanks again !

mdrussell
07-16-2002, 06:25 PM
You should tell James to check named.conf as it sounds as if the dns entries for your domain got screwed.

BeatYaBad
07-16-2002, 06:42 PM
James "screwed" the same thing for me and I have not heard back about the problem.

ceo
07-16-2002, 06:44 PM
Maybe he knows all that, and just is sitting back worried on how to handle so much support.

Anyways, I'll pass it on !

Icutwo
07-16-2002, 08:51 PM
The information that you have on that page is VERY INTERESTING!

Thankyou. :)

MCHost-Marc
07-16-2002, 10:02 PM
It says 'default page' here. Is that correct? If not, he needs to open /var/named/simonsaystraffic.com.db and change the IPs, then do a ndc reload.

meandean
07-16-2002, 10:10 PM
The problem is that James got rid of his former support team because it was one guy posing as four ...

... now they've got someone new either needs to get the DNS issues resolved (which I don't think is the case) ... or needs to understand how the virtual domains are configured.

The killer question being whether or not he's inherited a system that instantiates a separate httpd process for each site, or all the sites nder a single daemon process.

I would think for the sake of configration control they're running a single Apache process. If that is the case, they need to edit httpd.conf, ### Section 3:Virtual Hosts - from there, set up individual "containers" for each site ... Otherwise, they need to set up an httpd.conf for each and every site, virtual or otherwise.

What bothers me is that I haven't heard SQUAT from these guys since the weekend and now I'm falling behind in my projects waiting for them to get their act together.

... hey James - you've been responsive, generous and fair, but I need to hear from you NOW! Please, if you can't solve it or are insolvent then just tell me your host it toast and I'll call my $16.00 a loss and move on.

ceo
07-17-2002, 03:55 AM
Icutwo - Thank you, if only you would buy ; ) (kidding)

Kiwi - Thanks, but since it's one way communication I cannot move forward there !

meandean - I guess that's true (1 guy as 4). Sad but true.
Anyways, I've just decided to get hosting elsewhere for my site !
On my friends server - LOL