i creat my subdomains
such as web.xxx.com ,tools.xx.com
on enom.com
but when we visit web.xxx.com in my brower
it tell me no such address
what's the reason?

Hi there,
I'm unsure if you have the DNS settings entered correctly, but anyway, it takes time for the subdomain to propagate.

Why don't you update us again in 24 hours' time? ;)

i use default dns offered by enom,
i cann't visit my domain www.maopian.com after 48 hours i buy it
it's so strange.
cann't visit subdomain after 24 hours i created it

Just craete subdoamins at your hsot so much easier and works in seconds of setting it up.

Your DNS is either still resolving or all screwed up... I can't tell because it's really not my specialty. Checkout: http://dnsreport.com/tools/dnsreport.ch?domain=maopian.com

I think that it seems to still be resolving because it is inquiring both to enom's nameservers and also to NS/NS2.PIPNI.CZ

Maybe someone with more authority can jump in here. How about it guys?

Doing an nslookup on the domain, to all 13 root servers, shows enom's nameservers. The only place that there is a record of the ns/ns2.pipni.cz is actually within Enom's DNS.

All 5 of Enom's DNS are showing this.

I haven't personally used any of the DNS fucntions with Enom, so it's hard for me to say exactly what the problem is. Since you posted about 12 hours ago, it is possible that the DNS at Enom will update within another 12 hours or so (be sent out to the root servers), and then will continue to propagate.

Since you said you registered or at least updated the DNS over 48 hours ago, it would lead me to believe that either the DNS was entered incorrectly (as a setting in their DNS as opposed to as new Nameservers for your domain), or that there was an error when you updated to new nameservers.

To put it in semi english for you.
When someone looks for a website at their browser, they get sent to the root servers. The root servers are telling them to go to Enom to find your website, and enom is telling them that they aren't an authoritative source of information for the domain names, and that ns/ns2.pipni.cz is. The problem is, when it reaches Enom's DNS, that is the end of the line. It never actually goes over to ns/ns2.pipni.cz.

Doing an nslookup of pipni.cz shows their nameservers and IP addresses as ns/ns2.pipni.cz, so they are definately registered nameservers.

So, it's either a bad setting in the DNS with Enom, or Enom messed up when you tried to update the DNS for the domain. Again, it's hard to say exactly which, as i'm not familiar with how their DNS interface works.

So as 4solutions said, it's either still resolving, or it's all screwed up. It hasn't started to resolve, so it's all screwed up for sure. Just not sure exactly where.


Hope this helps,

Dan.