_:nf2b789ea1d05490a8ba10999febcf410xb3
<http://schema.org/text>
"So, DNS wise you appear to be mostly fine now. andreas@corrino:~$ dig googlexperience.com NS ; <<>> DiG 9.9.5-4.3ubuntu0.1-Ubuntu <<>> googlexperience.com NS ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36361 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;googlexperience.com. IN NS ;; ANSWER SECTION: googlexperience.com. 1651 IN NS ns3.digitalocean.com. googlexperience.com. 1651 IN NS ns2.digitalocean.com. googlexperience.com. 1651 IN NS ns1.digitalocean.com. ;; Query time: 64 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sun Jan 11 00:05:35 CET 2015 ;; MSG SIZE rcvd: 115 andreas@corrino:~$ dig www.googlexperience.com A ; <<>> DiG 9.9.5-4.3ubuntu0.1-Ubuntu <<>> www.googlexperience.com A ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53783 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.googlexperience.com. IN A ;; ANSWER SECTION: www.googlexperience.com. 1029 IN CNAME googlexperience.com. googlexperience.com. 1029 IN A 80.240.139.190 ;; Query time: 72 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sun Jan 11 00:14:21 CET 2015 ;; MSG SIZE rcvd: 82 andreas@corrino:~$ (The reason I say mostly fine is that I’m not a big fan of CNAMEs being used that way, even it will most likely be okey.) Can’t tell for sure from my end, but my guess would be that your initial problem with DNS lookups was due to TTL/caching issues."
<https://www.digitalocean.com/community/questions/err_name_not_resolved-changing-domain-why>