Figure out what DNS server your laptop is using (actually, looks like it is a local caching nameserver). Figure out what server your linode is using (should probably be the local Linode nameserver(s)) Figure out why they're different. You may find the dig tool to be more informative than nslookup:
Code:
$ dig @some.dnsserver.name applepatch.livingcosmos.org
; <<>> DiG 9.5.0-P2 <<>> applepatch.livingcosmos.org
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60618
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
;; QUESTION SECTION:
;applepatch.livingcosmos.org. IN A
;; ANSWER SECTION:
applepatch.livingcosmos.org. 86400 IN A 69.56.173.168
;; AUTHORITY SECTION:
livingcosmos.org. 86400 IN NS ns1.linode.com.
livingcosmos.org. 86400 IN NS ns2.linode.com.
livingcosmos.org. 86400 IN NS ns3.linode.com.
livingcosmos.org. 86400 IN NS ns4.linode.com.
;; Query time: 186 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Oct 10 16:47:38 2008
;; MSG SIZE rcvd: 143
So it looks like the Linode nameservers have the right data, but your linode is using them.[/code]