Why does WordPress' own nameserver not recognize that it's now my nameserver?
-
I started a blog about 36 hours ago, and purchased a mapped domain (for $13, as I already owned my own domain anme). On my registrar’s control panel (whois.com), I listed ns1,wordpress.com (and ns2 and ns3) as my domain’s nameservers. I then added the premium mapped domain on the WordPress site.
When I added the domain, the WordPress screen gleefully announced that my DNS was properly configured. However, any DNS (such as my home or office ISPs’ DNSs) from which I had previously accessed my domain name before I mapped it to WordPress won’t resolve my site name (http://andrewandbeatrice.com). Most (but not all) other DNSs do resolve it correctly. The WordPress name for the blog is andrewandbeatriceteenadvice.wordpress.com.
Also, when I did a “DIG” lookup of my site against WordPress’ nameserver (ns1.wordpress.com), I see that it still lists my old whois.com nameservers as the nameservers for the domain. Since I purchased domain mapping, I would have thought that a DIG against ns1.wordpress.com would have shown the 3 WordPress nameservers as my nameservers. Since 3 (!) hours have passed, I would have assumed your records would have been updated.
Have I done something wrong?
TIA
The blog I need help with is: (visible only to logged in users)
-
I should also add that if I do a DIG SOA query for andrewandbeatrice.com against ns1,wordpress.com, it thinks that ns1.whois.com is still the authority.
Help!
-
I’m seeing http://andrewandbeatrice.com/ point to your WordPress.com site. In all honesty, with DNS changes, it is usually just a matter of time before things shake out correctly. For whatever reason, things update slow sometimes and quicker sometimes.
Are you still having trouble with http://andrewandbeatrice.com/ not pointing where it should?
-
It’s still not working. And I was sure you’d succeed because almost everyone does. But again, my ISPs (my home ISP, my work ISP and a few other local ISPs) don’t.
Also, it makes no sense that a DIG of WordPress’ very own nameserver lists ns1.whois,com as the authority and not itself. I compared it with the record for the blog of a friend, judymintz.com. When I DIG her record on ns1.wordpress.com, I get the correct SOA as ns1.wordpress.com and not the nameserver of her registrar (GoDaddy). COuld you please try DIGging both her and my zone on ns1.wordpress.com to see why mine is different?
TIA
-
Still not working.
When I DIG andrewandbeatrice.com against ns1,wordpress.com, I get:
; <<>> DiG 9.9.3-P1 <<>> @ns1.wordpress.com andrewandbeatrice.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47770
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;andrewandbeatrice.com. IN A;; AUTHORITY SECTION:
andrewandbeatrice.com. 551 IN SOA ns1.whois.com. myemail.mymailserver.net. 2013071201 7200 7200 172800 38400;; Query time: 25 msec
;; SERVER: 72.233.69.14#53(72.233.69.14)
;; WHEN: Sat Jul 13 23:54:48 Jerusalem Daylight Time 2013
;; MSG SIZE rcvd: 118Why would a WordPress nameserver possibly list the registrar’s nameserver as the authority nameserver, when in fact WordPress is supposed to be the authority once I had my registrar list Word[ress’ 3 nameservers as the nameserver?
-
BTW – It has now been 48 hours already since I paid for the mapping, I wuld have expected no more DNS issues by now. And in any case, the fact that your nameservers list the whois.com nameservers as the authority is not going to get any better with time.
-
I can appreciate your frustration. But DNS propagation can take up to 72 hours.
Everything looks good from this end. And as far as I can tell, looks good worldwide at this point:
http://www.whatsmydns.net/#NS/andrewandbeatrice.com
However, if you are unsatisfied with the way that Domain Mapping is working, I will be happy to refund the upgrade purchase.
-
Hi Josh,
The problem was not propogation time per se, but rather the fact that it took WordPress’ own nameservers approx. 36 hours (!) to correctly update themselves (i.e., to specify themselves as the authority. That is ridiculously long.
This meant that any DNS which had ever previously resolved my domain before I pointed my domain’s namservers to WordPress got into trouble because it then pointed to your namservers, which sent them back erroneously wo ns1.whois.com.
In any case, it is now working.
-
Glad to hear that it is working. I’ve made notes of your comments and issue and will send them to the dev team. I have not heard of any systematic problem like this, but in case there are others reporting the same issue, it is good to keep a record.
- The topic ‘Why does WordPress' own nameserver not recognize that it's now my nameserver?’ is closed to new replies.
WordPress.com Forums 