Hi,

I decided to use blogger instead of tumblr and set about making the required changes last night, however I am not 100% if everything is correct.

For setting tumblr to point to my domain I had to add an A record only.

For blogger there are multiple A records and a CNAME as per http://www.google.com/support/blogger/b ... ts=1233381

Using the DNS Manager I have amended the setup as follows:

A/AAAA Records
Hostname: 'blank' - IP Address: 216.239.32.21
Hostname: 'blank' - IP Address: 216.239.34.21
Hostname: 'blank' - IP Address: 216.239.36.21
Hostname: 'blank' - IP Address: 216.239.38.21

CNAME Records
Hostname Aliases to TTL Options
Hostname: 'mail' - Aliases: ghs.google.com
Hostname: 'www' - Aliases: ghs.google.com

Its been ~ 30mins since amendments.

Running a dig www.mydomain.co.uk yields:

; <<>> DiG 9.7.0-P1 <<>> www.mydomain.co.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7753
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.mydomain.co.uk.   IN   A

;; ANSWER SECTION:
www.mydomain.co.uk. 85378 IN   CNAME   ghs.google.com.
ghs.google.com.      603129   IN   CNAME   ghs.l.google.com.
ghs.l.google.com.   31   IN   A   74.125.77.121

;; Query time: 29 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Thu Jun  2 10:50:08 2011
;; MSG SIZE  rcvd: 108

And dig @ns1.linode.com www.mydomain.co.uk:

; <<>> DiG 9.7.0-P1 <<>> @ns1.linode.com www.mydomain.co.uk
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15839
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;www.mydomain.co.uk.   IN   A

;; ANSWER SECTION:
www.mydomain.co.uk. 86400 IN   CNAME   ghs.google.com.

;; Query time: 135 msec
;; SERVER: 69.93.127.10#53(69.93.127.10)
;; WHEN: Thu Jun  2 10:52:46 2011
;; MSG SIZE  rcvd: 72

When I visit www.mydomain.co.uk it stills brings up tumblr and not blogger.

Blogger has been configured at its end.

Is this just a domain propagation issue or have I made a mistake?

Please help if you can.

Everything is working now, it must have been DNS propagation, America could see the changes before the UK.

Brief informational message from the DNS police:

DNS doesn't "propagate" per se, that could be interpreted as something actually pushing updates, instead resolver servers (ie, the kind of servers you would refer to in resolv.conf) are caching records that they have previously looked up until the TTL (Time To Live) value for the records expire and will continue to serve the cached records for subsequent queries from their clients.

Ie, the delay is caused by independently cached data in, possibly very many, caching servers that has to expire. The worst-case time it takes is dictated by the TTL value you set for the data on the authoritative servers.


Also, there is no relation between geographical distance (to what?) or geographical boundaries and when any given caching server will start to respond with your updated records.