Weird DNS behaviour

[Edgars Šmits]

While waiting for the install to complete I tried to use dig:

ubuntu at ubuntu:~$  dig +short www.vmware.com @192.168.0.1
;; Truncated, retrying in TCP mode.
;; Connection to 192.168.0.1#53(192.168.0.1) for www.vmware.com
failed: connection refused.

ubuntu at ubuntu:~$ dig +short www.gmail.com @192.168.0.1
mail.google.com.
googlemail.l.google.com.
66.249.91.83
66.249.91.19
66.249.91.17
66.249.91.18
ubuntu at ubuntu:~$

So, it has no problems with gmail, but the connection is refused for
www.vmware.com. I'm lost, where do I go now, there is no sysadmin
here, or more to the point, I'm the sysadmin<G>. Should I look for a
public DNS server close to home?

Cheers

On 10/25/07, Edgars Šmits <ed.smits at gmail.com> wrote:
> Thanks for the advice, I'll check into your suggestions later today.
> Right now I'm doing a clean install of Gutsy on my daughters laptop -
> using the LiveCD, and the problem still persists, so we know it's
> nothing to do with my laptop's Ubuntu DNS/TCPIP etc settings. I'll
> take this laptop to another location Saturday, see if the problem
> happens there as well.
>
> Very weird indeed...
>
> ED
>
> On 10/24/07, Rapael Morcha <raphael.morcha at gmail.com> wrote:
> > On Wed, Oct 24, 2007 at 06:21:53PM +0700, Fajar Priyanto wrote:
> > > On Wednesday 24 October 2007 11:00:32 Edgars Šmits wrote:
> > > > Glad someone took up the challenge...
> > > >
> > > > Nothing in my resolve.conf:
> > > >
> > > > edgars at gutsy-64:/etc$ more resolv.conf
> > > > # generated by NetworkManager, do not edit!
> > > > nameserver 192.168.0.1
> > > > edgars at gutsy-64:/etc$
> > > >
> > > > as to any dns related daemons, can't say that anything in there looks
> > > > to be of that sort.
> > > >
> > > > Anything else? It is specific only to Ubuntu.
> > >
> > > 192.168.0.1 is your dns server? If yes, then that's correct.
> > > Hmm, what else...
> > > 1. Check for network quality, by pinging your dns server or any other pc in
> > > the network for say a whole day and glance at the result whether there is any
> > > time out.
> > > 2. When you can't open certain website, try use the command dig to see whether
> > > it is your dns server that is having problem. Then try to dig with other dns
> > > server such as: dig www.ubuntu.com @ipofotherdnsserver
> >
> > As Fajar mentioned dig is helpful as well
> > $ dig +short www.somewww.com @ip.of.other.dns
> > (it should return list of resolved IP addresses of www.somewww.com)
> > If not, switch your DNS or talk to your admin.