Why can't I ping a subdomain I've just created?
I've just created a new subdomain for my yafz.org domain using DNS Manager.
Here's the output of my zone file:
; yafz.org [86804]
$TTL 86400
@ IN SOA ns1.linode.com. emre.sevinc.gmail.com. (
2010041335
14400
14400
1209600
86400
)
@ NS ns1.linode.com.
@ NS ns2.linode.com.
@ NS ns3.linode.com.
@ NS ns4.linode.com.
@ NS ns5.linode.com.
@ MX 10 mail.yafz.org.
@ A 109.74.204.147
www A 109.74.204.147
mail A 109.74.204.147
emre A 109.74.204.147
Now I'm connected to my server via SSH and I can ping yafz.org,
$ ping emre.yafz.org
ping: unknown host emre.yafz.org
$ ping yafz.org
PING yafz.org (109.74.204.147) 56(84) bytes of data.
64 bytes from li151-147.members.linode.com (109.74.204.147): icmp_seq=1 ttl=64 time=0.035 ms
64 bytes from li151-147.members.linode.com (109.74.204.147): icmp_seq=2 ttl=64 time=0.053 ms
$ ping mail.yafz.org
PING mail.yafz.org (109.74.204.147) 56(84) bytes of data.
64 bytes from li151-147.members.linode.com (109.74.204.147): icmp_seq=1 ttl=64 time=0.033 ms
I have created that new subdomain about 5-10 minutes ago. Should I wait more, or am I missing something?
6 Replies
→ ping emre.yafz.org
PING emre.yafz.org (109.74.204.147): 56 data bytes
64 bytes from 109.74.204.147: icmp_seq=0 ttl=52 time=120.824 ms
64 bytes from 109.74.204.147: icmp_seq=1 ttl=52 time=121.582 ms
64 bytes from 109.74.204.147: icmp_seq=2 ttl=52 time=120.739 ms
→ dig a emre.yafz.org
; <<>> DiG 9.4.3-P3 <<>> a emre.yafz.org
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27854
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;emre.yafz.org. IN A
;; ANSWER SECTION:
emre.yafz.org. 86269 IN A 109.74.204.147
;; Query time: 34 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Tue Apr 13 10:10:49 2010
;; MSG SIZE rcvd: 47
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:
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