Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm trying to configure a new domain in Plesk 9 on our dedicated server, but for some reason the subdomain webmail isn't loading, and a traceroute does not resolve. I tried making another subdomain, test, which also fails to resolve.

The domain name is lsbc.co

I'm not really sure where to start is the main issue. As far as I know there is know subdomain equivalent to intodns.com. And Google isn't helping discover where the settings for subdomains are stored in this situation.

I hope someone can assist,


share|improve this question

1 Answer 1

up vote 0 down vote accepted

It sounds like a DNS issue (if it doesn't resolve, the server isn't playing a part). Go to kloth.net and type in your domain name (without any subdomains) and select NS (nameserver) under the Query section. Hit lookup, and it will tell you where the DNS is stored for that domain.

You need to go to wherever that is and add subdomains (they make call them additional A records) for, at least, webmail.yourdomain.com. If you're lucky, they may even support adding wildcard DNS - add a subdomain of * and all subdomains not specifically mentioned will resolve to it.

To confirm it's a DNS issue, use kloth's A record lookup, or try to ping the subdomain - if it doesn't resolve (it should say PING domain.com (IP address) if it does), that's the issue. Don't worry too much if the PING times out as it could well be your hosting company blocking it.

EDIT: I just noticed you provided the domain in your question. I've checked and, as I thought, webmail.lsbc.co doesn't exist (** server can't find webmail.lsbc.co: NXDOMAIN). The DNS is hosted with 1and1 so you'll need to login to their control panel and add it there, if you have any issues they should be able to help.

share|improve this answer
Gah!! I've been messing about for the last two days trying to get to the bottom of this, my faulty assumption was of course that the domain name was actually pointing at our bloody nameservers. –  RubberDucky Nov 11 '10 at 20:04

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.