Re: resolv.conf

To: debian-user@lists.debian.org
Subject: Re: resolv.conf
From: John Hasler <jhasler@debian.org>
Date: Sun, 26 Dec 2004 11:41:39 -0600
Message-id: <[🔎] 87u0q9kld8.fsf@toncho.dhh.gt.org>
In-reply-to: <[🔎] 008601c4eb6b$265047c0$b9ef99ca@aviastar> (endianto@indo.net.id's message of "Sun, 26 Dec 2004 23:48:58 +0700")
References: <[🔎] 009a01c4eaeb$4dd3d940$e1ef99ca@aviastar> <[🔎] 1104047438.3326.2.camel@nmscow12.deven1.ov.home.nl> <[🔎] 004201c4eb25$09f6e7f0$7bef99ca@aviastar> <[🔎] 20041226121739.1c615f85@snoopy> <[🔎] 008601c4eb6b$265047c0$b9ef99ca@aviastar>

Try:

nameserver 202.158.20.1
nameserver 202.158.40.1
nameserver 202.159.33.2


But what do you mean by "never connected"?  What happens when you do

    ping 192.25.206.10
-- 
John Hasler

Reply to:

References:
- Fw: resolv.conf
  - From: "Endianto" <endianto@indo.net.id>
- Re: Fw: resolv.conf
  - From: John Smith <netman1@home.nl>
- Re: Fw: resolv.conf
  - From: "Endianto" <endianto@indo.net.id>
- Re: resolv.conf
  - From: Dani Belz <debian@dan-b.net>
- resolv.conf
  - From: "Endianto" <endianto@indo.net.id>

Prev by Date: Re: Linux Functionality?
Next by Date: Re: Help allocating RAM to video card
Previous by thread: Re: resolv.conf
Next by thread: Re: resolv.conf
Index(es):
- Date
- Thread