[plug] google.com

[Jon Miller]

Correct you are, I checked my /etc/resolv.conf file and it was missing my upstream DNS servers on our main network.  Wierd thing is how was it working before?

Anyway is well and that's what counts.

Thanks

Jon L. Miller, MCNE, CNS
Director/Sr Systems Consultant
MMT Networks Pty Ltd
http://www.mmtnetworks.com.au

"I don't know the key to success, but the key to failure
 is trying to please everybody." -Bill Cosby



>>> indy at THE-TECH.MIT.EDU 10:01:27 PM 31/05/2003 >>>

I only just looked into dig (nslookup may have been deprecated, but
I tend to go to it first still out of habit).

It would seem that dig feels like there is a nameserver problem too.


On Sat, May 31, 2003 at 09:21:44AM -0400, indy at the-tech.mit.edu wrote:
> 
> well, usually ping = unknown host
> indicates DNS issues.
> 
> 
> On Sat, May 31, 2003 at 09:23:19PM +0800, Jon  Miller wrote:
> > Well, I guess I got happy too quick, still cannot access google.com.  When I last reported I could it let me have a shot at it once, when I went back to do another search I was back where I started from.
> > So I did the following:
> > ping google.com, www.google.com, etc = unknown host
> > traceroute times out after I get to singapore
> > dig = 
> > ; <<>> DiG 9.2.1 <<>> www.google.com 
> > ;; global options:  printcmd
> > ;; connection timed out; no servers could be reached
> > [root at hm root]# dig google.com
> > 
> > ; <<>> DiG 9.2.1 <<>> google.com
> > ;; global options:  printcmd
> > ;; connection timed out; no servers could be reached
> > 
> > This is a real pisser.
> > 
> > Jon L. Miller, MCNE, CNS

-- 
Indranath Neogy
<indy at the-tech.mit.edu>