Quote:
Okay, one more time: DNS is updated now, and my site *should* be responding to pings to both addresses: 207.236.110.166 (old), and 64.26.128.89 (new).


Code:
[nathan@heorot nathan]$ dig rtr.ca

; <<>> DiG 9.2.1 <<>> rtr.ca
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28501
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 2

;; QUESTION SECTION:
;rtr.ca.                                IN      A

;; ANSWER SECTION:
rtr.ca.                 23604   IN      A       207.236.110.166

;; AUTHORITY SECTION:
rtr.ca.                 23604   IN      NS      ns2.granitecanyon.com.
rtr.ca.                 23604   IN      NS      ns1.rtr.ca.
rtr.ca.                 23604   IN      NS      ns1.granitecanyon.com.

;; ADDITIONAL SECTION:
ns1.granitecanyon.com.  153208  IN      A       205.166.226.38
ns2.granitecanyon.com.  153208  IN      A       69.67.108.10

;; Query time: 27 msec
;; SERVER: 192.168.168.2#53(192.168.168.2)
;; WHEN: Tue Nov  8 15:00:37 2005
;; MSG SIZE  rcvd: 143

[nathan@heorot nathan]$


So the new address is out there, but because of the TTL for the record anyone who did a lookup and got the old address is going to have to wait ~23604 seconds before that lookup expires from their local cache. (Or get their DNS server flushed, but most operators won't do that.)

So the folks who have been helpful before aren't going to be able to be of much help until that TTL expires.

--Nathan