[ale] Ahhhh. What is up with google

[mike at tyderia.net (Mike Murphy)]

If you want to ask your name server, just `dig google.com` (assuming the 
name server in question is what's in your /etc/resolv.conf, of course). 
What you might really want to do is ask another name server, so `dig 
google.com @ip.of.name.server` and compare your answers.

It may be that google had issues in the recent past, changed their name 
servers, and your name server doesn't have the update yet. If so, 
restarting it should fix that (generically speaking at least).

Mike


Christopher Fowler wrote:
> For some reason now I can not resolve google's address.
> 
> cfowler at linux:/tmp> ping -c1 www.google.com; ping -c1 www.yahoo.com
> ping: unknown host www.google.com
> PING www.yahoo.akadns.net (68.142.226.43) 56(84) bytes of data.
> 64 bytes from p12.www.re2.yahoo.com (68.142.226.43): icmp_seq=1 ttl=53
> time=92.5 ms
>  
> --- www.yahoo.akadns.net ping statistics ---
> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> rtt min/avg/max/mdev = 92.561/92.561/92.561/0.000 ms
> 
> 
> What is the correct dig command to get the correct server list for a
> caching only name server?  I've not updaetd mine in over 2 years and I
> think now it is a good time.
> 
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale