subdomain PB
-
Hello,
My subdomain cname mapping doesn’t work anymore : blog.darkless.fr CNAME darklessfr.wordpress.comTY
The blog I need help with is: (visible only to logged in users)
-
Hi there,
I’m able to see your site at your subdomain here: http://blog.darkless.fr/
Are you still having trouble with this? If you are, can you let me know what you see when you try to access your site at the link above? Thanks!
-
Yes that’s the problem,
CNAME is OK on my side,
when I ping blog.darkless.fr I get :
ping blog.darkless.fr
PING lb.wordpress.com (76.74.254.123) 56(84) bytes of data
64 bytes from . (76.74.254.123): icmp_req=1 ttl=53 time=122 msAnd I can not longer access to http://darklessfr.wordpress.com
-
# ping blog.darkless.fr
PING lb.wordpress.com (72.233.2.58) 56(84) bytes of data.
64 bytes from 58.2.233.72.static.reverse.ltdomains.com (72.233.2.58): icmp_req=1 ttl=47 time=111 ms -
Hi there, I have a few questions to help me troubleshoot this for you:
1. What do you see when you enter the following URLs in your web browser? (If you get a specific error message, please copy and paste it in your reply.)
2. Are you having trouble accessing the WordPress.com home page and other WordPress.com blogs? Or is the problem only with your blog?
3. To get to the bottom of this, it would also help for me to see a traceroute from your computer to our server at s0.wp.com. To get that information you’ll need to open the terminal app (inside the applications/utilities folder) and type the following command:
traceroute s0.wp.com
Please copy the full output of that command, and paste it in your reply.
If you have any questions, please let me know.
-
1. Server can’t be found
2.No, I can access to my admin console and modify my articles.
3.
$ traceroute s0.wp.com
traceroute to cs82.wac.edgecastcdn.net (93.184.220.111), 64 hops max, 52 byte packets
1 192.168.0.254 (192.168.0.254) 0.343 ms 0.167 ms 0.230 ms
2 * 213.228.23.254 (213.228.23.254) 32.026 ms 30.075 ms
3 lyon-6k-1-po1.intf.routers.proxad.net (212.27.56.209) 32.463 ms 34.019 ms 31.980 ms
4 th2-crs16-1-be2001.intf.routers.proxad.net (212.27.59.29) 35.555 ms 34.361 ms 37.677 ms
5 bzn-crs16-2-be2000.intf.routers.proxad.net (78.254.250.125) 38.694 ms 31.447 ms 31.999 ms
6 te0-1-0-3.363.mag21.par01.atlas.cogentco.com (149.6.160.97) 30.517 ms
te0-2-0-6.373.mag21.par01.atlas.cogentco.com (149.6.115.17) 30.562 ms
te0-2-0-5.371.mag21.par01.atlas.cogentco.com (149.6.115.5) 30.588 ms
7 prs-b2-link.telia.net (213.248.86.169) 29.518 ms 30.191 ms 30.517 ms
8 prs-bb1-link.telia.net (213.155.135.190) 39.899 ms
prs-bb1-link.telia.net (213.155.135.36) 30.573 ms
prs-bb2-link.telia.net (213.155.135.38) 30.552 ms
9 prs-b8-link.telia.net (213.155.131.9) 31.322 ms
prs-b8-link.telia.net (213.155.131.15) 30.508 ms 45.015 ms
10 edgecast-ic-153606-prs-b8.c.telia.net (80.239.195.14) 29.527 ms 31.231 ms 29.796 ms
11 93.184.220.111 (93.184.220.111) 30.242 ms 30.985 ms 29.581 msThanks
-
Hi there,
Based on your traceroute and the fact that you can access your WordPress.com dashboard normally, the problem is with your domain name rather than your connection to WordPress.com. It also seems to be a local issue, since I am able to access your site at blog.darkless.fr without any problems.
Can you please try flushing your DNS cache to see if that resolves the issue for you? If that doesn’t work, you may need to contact your ISP and ask them to flush their DNS cache.
Please let me know if you have any questions about that.
-
- The topic ‘subdomain PB’ is closed to new replies.
WordPress.com Forums 