DNS error - cannot find server

[Christy]

hi friends, 

  

i have been getting error while surfing as "DNS error - cannot find server"  on Ubuntu 9.04 since yesterday. 

i googled and found that the error is usually caused due to problem on local machine. 

hence i tried surfing on windows (dual boot) and found everything working fine.

also all soln i have encountered on google is meant for windows. its says something abt flushing dns or so. 

has anyone on grp encountered it before or know the soln (for linux). 

i thought it was a bug and so tried updating but got error regarding some signatures. 

I do not wish to surf on Windows since its prone to viruses,trojans,etc....

a quick soln would be appreciated. 

if i encounter a soln. ill post it. 

 

thx

--
By,

Christopher U

[Niranjan Mujumdar]

I think flushing DNS should solve it.
Try

sudo /etc/init.d/nscd restart

If nscd is not there, install it.

Nir

> --
> Email to group : dbit-t...@googlegroups.com
> To unsubscribe, send email to
> dbit-techtal...@googlegroups.com
> Visit this group at
> http://groups.google.com/group/dbit-techtalk?hl=en

[Sreepathi Pai]

On Thu, Feb 4, 2010 at 11:01 PM, Niranjan Mujumdar <niran...@gmail.com> wrote:
> I think flushing DNS should solve it.
> Try
>
> sudo /etc/init.d/nscd restart
>
> If nscd is not there, install it.

NSCD has *nothing* to do with DNS. Atleast, it's not the first thing
you'll check for.

Make sure your DNS servers are configured by examining the contents of
/etc/resolv.conf or /etc/resolv.conf.d

Try running the host command:

$ host www.google.com

And send it's output.

--
Sreepathi Pai

[Christy]

hi,

sree is right abt nscd as it didnt change anything.

under /etc/resolv.conf it given as

nameserver 172.**.**.*

nameserver 202.***.***.***

Running the host command:

christy@workstation:~$ host www.google.com

www.google.com is an alias for www.l.google.com.

www.l.google.com has address 209.85.231.147

www.l.google.com has address 209.85.231.104

www.l.google.com has address 209.85.231.99

the problem persists. i can view some sites in Ubuntu, like gmail.com,google.com. but if i click on any search links it gives error. the site rediff.com is viewable at times randomly. [ these are symptoms occuring ]

--

Email to group :  dbit-t...@googlegroups.com
To unsubscribe, send email to
dbit-techtal...@googlegroups.com
Visit this group at
http://groups.google.com/group/dbit-techtalk?hl=en

--
By,

Christopher U,
SD,
DBIT.

[Christy]

under /etc/resolv.conf it given as

nameserver 172.30.70.1

nameserver 202.177.240.251

[Njoy]

Did u try ubuntuforums i think there could be lot of folks out there
who could help u
try posting it there and also the link of that post here

On Feb 5, 8:30 pm, Christy <christopher...@gmail.com> wrote:
> under /etc/resolv.conf it given as
>
> nameserver 172.30.70.1
> nameserver 202.177.240.251
>
>
>
>
>
> On Fri, Feb 5, 2010 at 1:03 PM, Christy <christopher...@gmail.com> wrote:
> > hi,
>
> > sree is right abt nscd as it didnt change anything.
>
> > under /etc/resolv.conf it given as
>
> > nameserver 172.**.**.*
> > nameserver 202.***.***.***
>
> > Running the host command:
>
> > christy@workstation:~$ hostwww.google.com
> >www.google.comis an alias forwww.l.google.com.
> >www.l.google.comhas address 209.85.231.147
> >  www.l.google.comhas address 209.85.231.104

> >www.l.google.comhas address 209.85.231.99

>
> > the problem persists. i can view some sites in Ubuntu, like gmail.com,
> > google.com. but if i click on any search links it gives error. the site
> > rediff.com is viewable at times randomly. [ these are symptoms occuring ]
>

> > On Fri, Feb 5, 2010 at 9:16 AM, Sreepathi Pai <sree...@gmail.com> wrote:
>
> >> On Thu, Feb 4, 2010 at 11:01 PM, Niranjan Mujumdar <niranja...@gmail.com>

> >> wrote:
> >> > I think flushing DNS should solve it.
> >> > Try
>
> >> > sudo /etc/init.d/nscd restart
>
> >> > If nscd is not there, install it.
>
> >> NSCD has *nothing* to do with DNS. Atleast, it's not the first thing
> >> you'll check for.
>
> >> Make sure your DNS servers are configured by examining the contents of
> >> /etc/resolv.conf or /etc/resolv.conf.d
>
> >> Try running the host command:
>
> >> $ hostwww.google.com
>
> >> And send it's output.
>
> >> --
> >> Sreepathi Pai
>
> >> --
> >> Email to group :  dbit-t...@googlegroups.com
> >> To unsubscribe, send email to

> >> dbit-techtal...@googlegroups.com<dbit-techtalk%2Bunsubscribe@goog legroups.com>

[Lincoln Fernandes]

Use the peoples favorite

4.2.2.2 DNS server and evrything should work fine!!

[Christy]

hi freinds,

i think i got to the root of problem it has to do with resolv.conf.

now with the current value given below everything seems fine. 

nameserver 202.177.240.251

nameserver 202.177.240.250 

i would like to note here that these values were retrieved from the server automatically.

In windows even after rebooting twice it always take 202* values. while in ubuntu it uses 172.* at times after rebooting.

the problem ariseses when it gets the DNS server '172.30.70.1', giving DNS error.  

to test this i maually changed the resolv.conf commenting 172.*.*.* and adding 202.177.240.250. 

and guess what it started working fine didnt have to restart the network.

the following is value in file resolv.conf

nameserver 202.177.240.251

nameserver 202.177.240.250 

#nameserver 172.30.70.1

now the only challenge remains is to permanently write these values in resolv.conf. although after rebooting once after commeting the line, the values havent changed. 

so i dont know whether the values will change again in future. 

i am happy i didnt had to resort to last soln i.e Reinstalling Ubuntu, although i had doubts abt it solving the prob.  

anyway thx sree,niranjan and lincoln for helping out. 

Techtalk is alive again. 

[Savio Monteiro]

in your /etc/network/interfaces add the following line ... under ur ethernet (mostly eth0) line like this ... 

under the line that says ... iface eth0 inet dhcp

add ...

up echo nameserver 202.177.240.251 > /etc/resolv.conf

up echo nameserver 202.177.240.250 >> /etc/resolv.conf

and save it ... rerun 

$ sudo /etc/init.d/networking restart

Savio.

[Savio Monteiro]

also i am assuming u are in the dbit network ... which again i assume has not changed much after we've been away ... 

Savio.

[Christy]

noop this is at my home PC

[Savio Monteiro]

hmm well it'll work ... 

[Sreepathi Pai]

Assuming you're using a DSL router, check its configuration and enable
the option to refuse DNS server addresses from DHCP. Instead use your
own addresses. In fact, you could probably use 8.8.8.8 (which is
Google DNS). You do not have to modify anything on your PC.

On Sat, Feb 6, 2010 at 12:28 PM, Savio Monteiro <savi...@gmail.com> wrote:
> hmm well it'll work ...
>

> On Sat, Feb 6, 2010 at 12:39 AM, Christy <christo...@gmail.com> wrote:
>>
>> noop this is at my home PC
>>
>> On Sat, Feb 6, 2010 at 11:33 AM, Savio Monteiro <savi...@gmail.com>
>> wrote:
>>>
>>> also i am assuming u are in the dbit network ... which again i assume has
>>> not changed much after we've been away ...
>>> Savio.
>>>
>>> On Sat, Feb 6, 2010 at 12:02 AM, Savio Monteiro <savi...@gmail.com>
>>> wrote:
>>>>
>>>> in your /etc/network/interfaces add the following line ... under ur
>>>> ethernet (mostly eth0) line like this ...
>>>> under the line that says ... iface eth0 inet dhcp
>>>> add ...
>>>> up echo nameserver 202.177.240.251 > /etc/resolv.conf
>>>> up echo nameserver 202.177.240.250 >> /etc/resolv.conf
>>>> and save it ... rerun
>>>> $ sudo /etc/init.d/networking restart
>>>>
>>>> Savio.

>>>> On Fri, Feb 5, 2010 at 11:31 PM, Christy <christo...@gmail.com>

--
Sreepathi Pai

[Savio Monteiro]

Yea this works too ..

Savio Monteiro

On Feb 7, 2010 8:04 AM, "Sreepathi Pai" <sre...@gmail.com> wrote:

Assuming you're using a DSL router, check its configuration and enable
the option to refuse  DNS server addresses from DHCP. Instead use your
own addresses. In fact, you could probably use 8.8.8.8 (which is
Google DNS). You do not have to modify anything on your PC.

On Sat, Feb 6, 2010 at 12:28 PM, Savio Monteiro <savi...@gmail.com> wrote: > hmm well it'll work ...

Visit this group at http://groups.google.com/group/dbit-techtalk?hl=en

[Christy]

i am not using a DSL router. BTW everything is working fine since last 2 days. the prob is solved. thx everyone again. 

On Sun, Feb 7, 2010 at 7:34 PM, Sreepathi Pai <sre...@gmail.com> wrote:

Assuming you're using a DSL router, check its configuration and enable
the option to refuse  DNS server addresses from DHCP. Instead use your
own addresses. In fact, you could probably use 8.8.8.8 (which is
Google DNS). You do not have to modify anything on your PC.

On Sat, Feb 6, 2010 at 12:28 PM, Savio Monteiro <savi...@gmail.com> wrote:
> hmm well it'll work ...
>

> On Sat, Feb 6, 2010 at 12:39 AM, Christy <christopher.uz@gmail.com> wrote:
>>
>> noop this is at my home PC
>>
>> On Sat, Feb 6, 2010 at 11:33 AM, Savio Monteiro <savi...@gmail.com>
>> wrote:
>>>
>>> also i am assuming u are in the dbit network ... which again i assume has
>>> not changed much after we've been away ...
>>> Savio.
>>>
>>> On Sat, Feb 6, 2010 at 12:02 AM, Savio Monteiro <savi...@gmail.com>
>>> wrote:
>>>>
>>>> in your /etc/network/interfaces add the following line ... under ur
>>>> ethernet (mostly eth0) line like this ...
>>>> under the line that says ... iface eth0 inet dhcp
>>>> add ...
>>>> up echo nameserver 202.177.240.251 > /etc/resolv.conf
>>>> up echo nameserver 202.177.240.250 >> /etc/resolv.conf
>>>> and save it ... rerun
>>>> $ sudo /etc/init.d/networking restart
>>>>
>>>> Savio.

>>>> On Fri, Feb 5, 2010 at 11:31 PM, Christy <christopher.uz@gmail.com>