It's resolving fine from here too:
Code:
rtucker@arrogant-bastard:~$ dig emre.yafz.org
; <<>> DiG 9.6.1-P2 <<>> emre.yafz.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11069
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;emre.yafz.org. IN A
;; ANSWER SECTION:
emre.yafz.org. 86400 IN A 109.74.204.147
;; Query time: 115 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Tue Apr 13 12:54:38 2010
;; MSG SIZE rcvd: 47
I note that the negative caching TTL is 86400 seconds for yafz.org, which means that your local nameserver is permitted to cache the fact that emre.yafz.org doesn't exist for up to 24 hours. Odds are good you tried checking it before it went live on the nameservers, and thus, you're caching.
(The last number in the SOA:
Code:
rtucker@arrogant-bastard:~$ dig yafz.org SOA +short
ns1.linode.com. emre.sevinc.gmail.com. 2010041337 14400 14400 1209600 86400
... is the negative caching TTL.)
Quick solution: try again tomorrow

-rt