Hi,

I just got a new dedicated server with Cpanel + WHM installed on it. Nameservers and everything else were supposed to be setup by our provider burst.net and looking around the setup they seem OK. I created a service plan, setup a site and login to the user cpanel fine. However when I go to create subdomains I get the following error:

"anything.mydomain.com could not be modified because it does not resolve to a valid ip address. Ignore any messages of success this can only result in failure!"

Cpanel adds a DNS entry for the subdomain but doesn't create the directory in the userspace. Subdomains are definitely enabled on the account. I've tried setting up separate domain accounts on the server and I still get the same error. I know this is not a domain propagation issue because I can setup subdomains on a virtual cpanel account I have with venturesonline - and that domain is not pointing to their server.

This morning I got a logcheck mail back and it shows the following:

May 12 21:45:07 server named[1663]: lame server on 'anything.mydomain.com.darkorb.net' (in 'DARKORB.net'?): 205.162.50.249#53

Can anyone help me with this problem? I've been at it for hours without any success whatsoever. I'd be most grateful! :D

I'm pretty sure that subdomains only work on an account that has been setup on a unique IP. If you set it up on a shared IP you will receive that message.

It has been setup on a dedicated IP. I've tested sites on both shared and dedicated IPs and I still get the same errors.

The Subdomains Need To Be Enabled Through WHM with the "Disable or Enable Subdomains Per Account " option in the Menu !

I Also Got My Server A Few Hours Ago From Burst.Net & they were supposed to setup nameservers but I Do Not Happen To Know The IPs of the Nameservers. I need them in order to Register The Nameservers with My Domain Name's Registrar Can You Tell Me How Did You Come To Know Of Those IPs ?
Regards
KG

If they have already been setup for you just check the zone file for the domain that you setup nameservers with. For example. if you created the nameservers:

ns.yourdomain.com
ns2.yourdomain.com

Just take a look at the zone file for yourdomain.com by:

cat /var/named/yourdomain.com.db

You'll see the IP's that your nameservers have been assigned because you'll see two entries like:

ns 1800 IN A 157.223.46.226
ns2 1800 IN A 157.223.46.227

... a little late as tabernack beat me to the reply ....

but to find the ip's via WHM (vs. SSH):

simply look at the zone file for the domain that the name servers were set up on.

ex: if your domain for the name servers is 'what.com' then just log into the WHM and click in the 'edit a DNS Zone & choose the what.com domain from the list. from here, you will be able to see an entry for both of the name servers with the correcponding ip's.

hope this helps.

Originally posted by koolguru
The Subdomains Need To Be Enabled Through WHM with the "Disable or Enable Subdomains Per Account " option in the Menu !

Yep already tried doing that too. Still the same results and same errors. Adds the DNS entry okay but reports the above error and doesn't create the directory in our virtual site.

Californian, maybe it's time to fire a support ticket to Burst. Please give us update whether your problem has been solved or not.

I fired off a support ticket to the burst.net people before I even posted here. As of yet I still haven't heard anything back from them. I also noticed some more problems:

Custom error pages are not working.
Disk quotas and bandwidth usage are not updating.

Hopefully they'll look into this at somepoint today.

Still nil reply from Burst.net about our cpanel problem. I have noticed when I try adding a sub-domain it's using a different IP address to the one originally setup for the website. And it's not even the IP address of the server which its trying to use. I'm now assuming this is the core of the problem.

Anyone have any ideas why cpanel would use a different IP address as to the one I set as the dedicated IP for the site in question? Since the IP its using is not being used by any other site on the box I believe this would explain the error: "anything.mydomain.com could not be modified because it does not resolve to a valid ip address. Ignore any messages of success this can only result in failure!"

This is really annoying me now.

Check the IP in /etc/wwwacct.conf
Make sure it is the correct one for your primary servre IP.

What is your ticket number?

Sean R.
BurstNET

Sean,

The IP is correct in that file. Our unanswered ticket # is: 19014.

Californian,

Keep us posted. I'd like to know how it ended.

Well since I posted my follow up here regarding our unanswered ticket I still haven't heard anything from burst.net about our problem. A couple of days ago I sent an email to sean personally about it and he hasn't replied either.

This is unfortunate because the performance of our server is excellent and burst's new data center seems to be performing exceptionally well. But the fact that I can't get hold of support when I need them is rather worrying.

I have tried phoning their support and experienced the same problem as others mentioned in previous threads. The phone just rings off eachtime to their voicemail box. I sent numerous messages to them on ICQ asking them to look this up and nothing.

So a few seconds later I move on to their website and click the "Talk to a Burst.net sales person" and within seconds there is Sean ready to answer my questions. To say this bothered me would be a major understatement.

I'm at my wits end at what to do next.

Did Sean talk to you after connecting through the sales person link? Story seemed to end abruptly ...
:confused:

C'mon man, don't keep us hangin
:)

It sounds like he's mad because he thinks sales was available right away, while he was having a very hard time getting ahold of support. Obviously, this would cause some frustration since the customer would thing the web host is more focused on sales than supporting their current customers.

Where is this mydomain.com coming from?? Are you sure that the user has a domain set? Or the domain actually mydomain.com?