[Gllug] nslookup resolves but not ping or http

[gvim]

On 07/12/2010 15:51, John Edwards wrote:
> On Tue, Dec 07, 2010 at 03:40:27PM +0000, gvim wrote:
  
> Sounds like something is caching negative results, either a DNS server
> that the machine is using or something running on your machine (eg
> nscd).
>
> The hostname resolves fine for me:
> --------
> $ host wikileaks.dbpro.org.uk
> wikileaks.dbpro.org.uk has address 80.68.88.120
> wikileaks.dbpro.org.uk mail is handled by 20 backup.mx.bytemark.co.uk.
> wikileaks.dbpro.org.uk mail is handled by 10 a.mx.wikileaks.dbpro.org.uk.
> $ ping -c 3 wikileaks.dbpro.org.uk
> PING wikileaks.dbpro.org.uk (80.68.88.120) 56(84) bytes of data.
> 64 bytes from danisrael.vm.bytemark.co.uk (80.68.88.120): icmp_seq=1 ttl=56 time=33.7 ms
> 64 bytes from danisrael.vm.bytemark.co.uk (80.68.88.120): icmp_seq=2 ttl=56 time=34.5 ms
> 64 bytes from danisrael.vm.bytemark.co.uk (80.68.88.120): icmp_seq=3 ttl=56 time=34.4 ms
>
> --- wikileaks.dbpro.org.uk ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2001ms
> rtt min/avg/max/mdev = 33.774/34.249/34.556/0.340 ms
> --------
>

Resolved now but for a while dig/nslookup on my Snow Leopard machine was resolving where ping & http couldn't. I was sure it was a propagation issue but wanted to understand the mechanics of how one tool could resolve before another.

gvim
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug