Hi, and Welcome to Ubuntu forums. That is a really good question and I have wondered about it also several times. I do not know the root answer. However...
You will find with some of these huge very busy sites that they a very short minimum TTL (Time To Live). Example of how to check:
Code:
doug@doug-64:~$ dig -t SOA google.com
; <<>> DiG 9.8.1-P1 <<>> -t SOA google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4799
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 0
;; QUESTION SECTION:
;google.com. IN SOA
;; ANSWER SECTION:
google.com. 83634 IN SOA ns1.google.com. dns-admin.google.com. 2013031900 7200 1800 1209600 300
;; AUTHORITY SECTION:
. 323312 IN NS g.root-servers.net.
...[deleted]...
. 323312 IN NS d.root-servers.net.
;; Query time: 2 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Mar 20 11:58:59 2013
;; MSG SIZE rcvd: 289
Where 300 seconds is the minimum TTL. Next do a regular lookup:
Code:
doug@doug-64:~$ dig google.com
; <<>> DiG 9.8.1-P1 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20057
;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 13, ADDITIONAL: 0
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 198 IN A 173.194.33.0
google.com. 198 IN A 173.194.33.1
google.com. 198 IN A 173.194.33.2
google.com. 198 IN A 173.194.33.3
google.com. 198 IN A 173.194.33.4 <<< I have no idea why only the 8 turned red here
google.com. 198 IN A 173.194.33.5
google.com. 198 IN A 173.194.33.6
google.com. 198 IN A 173.194.33.7
google.com. 198 IN A 173.194.33.8
google.com. 198 IN A 173.194.33.9
google.com. 198 IN A 173.194.33.14
;; AUTHORITY SECTION:
. 323144 IN NS k.root-servers.net.
...[deleted]...
. 323144 IN NS g.root-servers.net.
;; Query time: 36 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Mar 20 12:01:47 2013
;; MSG SIZE rcvd: 415
For whatever reason the cache time for this will be 198 seconds, and it is not always the same. I.E. if I run the same command 10 seconds later the time left will show as 188 seconds and the Query time will be 0.
So, now let us try a lesser type site:
Code:
doug@doug-64:~$ dig -t SOA bcferries.com
; <<>> DiG 9.8.1-P1 <<>> -t SOA bcferries.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50806
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 0
;; QUESTION SECTION:
;bcferries.com. IN SOA
;; ANSWER SECTION:
bcferries.com. 3600 IN SOA mns01.domaincontrol.com. dns.jomax.net. 2013013000 28800 7200 604800 86400
;; AUTHORITY SECTION:
. 323588 IN NS j.root-servers.net.
...[deleted]...
. 323588 IN NS i.root-servers.net.
;; Query time: 111 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Mar 20 11:54:23 2013
;; MSG SIZE rcvd: 308
Code:
doug@doug-64:~$ dig bcferries.com
; <<>> DiG 9.8.1-P1 <<>> bcferries.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45376
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 0
;; QUESTION SECTION:
;bcferries.com. IN A
;; ANSWER SECTION:
bcferries.com. 30325 IN A 69.90.97.140
;; AUTHORITY SECTION:
. 323604 IN NS e.root-servers.net.
... [deleted]...
. 323604 IN NS a.root-servers.net.
;; Query time: 47 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Mar 20 11:54:07 2013
;; MSG SIZE rcvd: 258
And much later (just over 20 minutes) again:
Code:
; <<>> DiG 9.8.1-P1 <<>> bcferries.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43904
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 0
;; QUESTION SECTION:
;bcferries.com. IN A
;; ANSWER SECTION:
bcferries.com. 29015 IN A 69.90.97.140
;; AUTHORITY SECTION:
. 322294 IN NS l.root-servers.net.
...[deleted]...
. 322294 IN NS b.root-servers.net.
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Mar 20 12:15:57 2013
;; MSG SIZE rcvd: 258
Hope this helps.
Bookmarks