Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.raspberry-pi > #9459 > unrolled thread

resolv.conf problem

Back to article view | Back to comp.sys.raspberry-pi

Contents

  resolv.conf problem Adrian <bulleid@ku.gro.lioff> - 2015-08-21 17:01 +0100
    Re: resolv.conf problem Rob Morley <nospam@ntlworld.com> - 2015-08-21 17:12 +0100
      Re: resolv.conf problem Adrian <bulleid@ku.gro.lioff> - 2015-08-21 20:42 +0100
        Re: resolv.conf problem Roger Bell_West <roger+csrp201508@nospam.firedrake.org> - 2015-08-21 20:42 +0000
          Re: resolv.conf problem Adrian <bulleid@ku.gro.lioff> - 2015-08-21 22:32 +0100
    Re: resolv.conf problem ray carter <ray@zianet.com> - 2015-08-21 16:29 +0000
      Re: resolv.conf problem Adrian <bulleid@ku.gro.lioff> - 2015-08-21 20:42 +0100
        Re: resolv.conf problem Knute Johnson <nospam@rabbitbrush.frazmtn.com> - 2015-08-21 22:19 -0700
          Re: resolv.conf problem Adrian <bulleid@ku.gro.lioff> - 2015-08-22 20:42 +0100
            Re: resolv.conf problem Torfinn Ingolfsen <tingo@home.no> - 2015-08-23 20:57 +0200
              Re: resolv.conf problem Adrian <bulleid@ku.gro.lioff> - 2015-08-23 22:49 +0100
                Re: resolv.conf problem Morten Reistad <first@last.name.invalid> - 2015-08-24 10:42 +0200
                  Re: resolv.conf problem "A. Dumas" <alexandre@dumas.fr.invalid> - 2015-08-24 11:12 +0200
                    Re: resolv.conf problem Morten Reistad <first@last.name.invalid> - 2015-08-24 11:19 +0200
              Re: resolv.conf problem DisneyWizard the Fantasmic! <wiz@FANTASMIC!disneywizard.com> - 2015-08-23 20:25 -0700
                Re: resolv.conf problem Kees Theunissen <theuniss@rijnh.nl> - 2015-08-27 04:49 +0200
                  Re: resolv.conf problem Adrian <bulleid@ku.gro.lioff> - 2015-08-27 20:35 +0100
                    Re: resolv.conf problem "A. Dumas" <alexandre@dumas.fr.invalid> - 2015-08-28 09:16 +0200
                      Re: resolv.conf problem Dave Higton <dave@davehigton.me.uk> - 2015-08-28 20:48 +0100
        Re: resolv.conf problem David <wibble@btintenet.com> - 2015-08-29 18:33 +0000
    Re: resolv.conf problem ray carter <ray@zianet.com> - 2015-08-21 16:34 +0000

Page 1 of 2  [1] 2  Next page →

#9459 — resolv.conf problem

I'm having "fun" with a Pi 2 when it is using WiFi rather than Ethernet.


On Ethernet, it appears to boot up, and pick up the time server OK, but 
on WiFi, it doesn't.  Doing some digging around on line, the suggestions 
seem to centre on making sure that the /etc/resolv.conf file has name 
servers in it.

I've edited the file to put in a number of entries (cut and paste from a 
Pi B+), and the Pi 2 picks up the time server, and away we go.  As soon 
as I reboot, we are back to the same problem.  It seems that either the 
shutdown or the boot operation empties the file and puts :

# Generated by resolvconf

in the file instead, which is starting to get annoying.

Strangely, the Pi 2 has a /etc/resolv.conf and a /etc/resolvconf.conf 
file, whereas the B+ only has the former.  Should I get rid of the 
latter file ?

Both machines are running raspbian.

Adrian
-- 
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

[toc] | [next] | [standalone]

#9460

On Fri, 21 Aug 2015 17:01:26 +0100
Adrian <bulleid@ku.gro.lioff> wrote:

> I'm having "fun" with a Pi 2 when it is using WiFi rather than
> Ethernet.
> 
> 
> On Ethernet, it appears to boot up, and pick up the time server OK,
> but on WiFi, it doesn't.  Doing some digging around on line, the
> suggestions seem to centre on making sure that the /etc/resolv.conf
> file has name servers in it.
> 
> I've edited the file to put in a number of entries (cut and paste
> from a Pi B+), and the Pi 2 picks up the time server, and away we
> go.  As soon as I reboot, we are back to the same problem.  It seems
> that either the shutdown or the boot operation empties the file and
> puts :
> 
> # Generated by resolvconf
> 
> in the file instead, which is starting to get annoying.
> 
> Strangely, the Pi 2 has a /etc/resolv.conf and a /etc/resolvconf.conf 
> file, whereas the B+ only has the former.  Should I get rid of the 
> latter file ?
> 
Maybe you should edit that one instead and see if it gets copied over.

[toc] | [prev] | [next] | [standalone]

#9465

In message <20150821171206.36b2973e@ntlworld.com>, Rob Morley 
<nospam@ntlworld.com> writes
>On Fri, 21 Aug 2015 17:01:26 +0100
>Adrian <bulleid@ku.gro.lioff> wrote:
>
>> I'm having "fun" with a Pi 2 when it is using WiFi rather than
>> Ethernet.
>>
>>
>> On Ethernet, it appears to boot up, and pick up the time server OK,
>> but on WiFi, it doesn't.  Doing some digging around on line, the
>> suggestions seem to centre on making sure that the /etc/resolv.conf
>> file has name servers in it.
>>
>> I've edited the file to put in a number of entries (cut and paste
>> from a Pi B+), and the Pi 2 picks up the time server, and away we
>> go.  As soon as I reboot, we are back to the same problem.  It seems
>> that either the shutdown or the boot operation empties the file and
>> puts :
>>
>> # Generated by resolvconf
>>
>> in the file instead, which is starting to get annoying.
>>
>> Strangely, the Pi 2 has a /etc/resolv.conf and a /etc/resolvconf.conf
>> file, whereas the B+ only has the former.  Should I get rid of the
>> latter file ?
>>
>Maybe you should edit that one instead and see if it gets copied over.
>

Thanks.

I've tried that, and it doesn't get copied over, I still end up with a 
file with a comment in, and nothing else.

Adrian
-- 
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

[toc] | [prev] | [next] | [standalone]

#9466

On 2015-08-21, Adrian wrote:
>I've tried that, and it doesn't get copied over, I still end up with a 
>file with a comment in, and nothing else.

Is your DHCP server actually giving out nameserver addresses
correctly? I've had no problems with resolvconf.

You could always put an explicit dns-nameservers directive in your
/etc/network/interfaces (in the iface wlan0 stanza). You are using
plain /etc/network/interfaces not Network Manager or some such horror,
right?

[toc] | [prev] | [next] | [standalone]

#9467

In message <20150821214120.375888471798138@firedrake.org>, Roger 
Bell_West <roger+csrp201508@nospam.firedrake.org> writes
>Is your DHCP server actually giving out nameserver addresses
>correctly? I've had no problems with resolvconf.
>

Pass, sorry I wouldn't know how to check.

>You could always put an explicit dns-nameservers directive in your
>/etc/network/interfaces (in the iface wlan0 stanza). You are using
>plain /etc/network/interfaces not Network Manager or some such horror,
>right?

I'm using whatever it runs "out of the box".

I've added a directive to the /etc/network/interfaces file, and after 
rebooting, it is working.

Thanks for your assistance and from the others to reply to this thread.


Adrian
-- 
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

[toc] | [prev] | [next] | [standalone]

#9461

On Fri, 21 Aug 2015 17:01:26 +0100, Adrian wrote:

> I'm having "fun" with a Pi 2 when it is using WiFi rather than Ethernet.
> 
> 
> On Ethernet, it appears to boot up, and pick up the time server OK, but
> on WiFi, it doesn't.  Doing some digging around on line, the suggestions
> seem to centre on making sure that the /etc/resolv.conf file has name
> servers in it.
> 
> I've edited the file to put in a number of entries (cut and paste from a
> Pi B+), and the Pi 2 picks up the time server, and away we go.  As soon
> as I reboot, we are back to the same problem.  It seems that either the
> shutdown or the boot operation empties the file and puts :
> 
> # Generated by resolvconf
> 
> in the file instead, which is starting to get annoying.
> 
> Strangely, the Pi 2 has a /etc/resolv.conf and a /etc/resolvconf.conf
> file, whereas the B+ only has the former.  Should I get rid of the
> latter file ?
> 
> Both machines are running raspbian.
> 
> Adrian

Does this help:

http://unix.stackexchange.com/questions/216774/keep-losing-resolv-conf-
configurations

[toc] | [prev] | [next] | [standalone]

#9464

In message <d3p1vmFk0ffU12@mid.individual.net>, ray carter 
<ray@zianet.com> writes
>On Fri, 21 Aug 2015 17:01:26 +0100, Adrian wrote:
>
>> I'm having "fun" with a Pi 2 when it is using WiFi rather than Ethernet.
>>
>>
>> On Ethernet, it appears to boot up, and pick up the time server OK, but
>> on WiFi, it doesn't.  Doing some digging around on line, the suggestions
>> seem to centre on making sure that the /etc/resolv.conf file has name
>> servers in it.
>>
>> I've edited the file to put in a number of entries (cut and paste from a
>> Pi B+), and the Pi 2 picks up the time server, and away we go.  As soon
>> as I reboot, we are back to the same problem.  It seems that either the
>> shutdown or the boot operation empties the file and puts :
>>
>> # Generated by resolvconf
>>
>> in the file instead, which is starting to get annoying.
>>
>> Strangely, the Pi 2 has a /etc/resolv.conf and a /etc/resolvconf.conf
>> file, whereas the B+ only has the former.  Should I get rid of the
>> latter file ?
>>
>> Both machines are running raspbian.
>>
>> Adrian
>
>Does this help:
>
>http://unix.stackexchange.com/questions/216774/keep-losing-resolv-conf-
>configurations

Thanks, sort of.

ps -A | grep -i dhc

gives me different answers on different machines.  The Pi B+ (which is 
OK and on Ethernet) gives dhclient, whereas the Pi 2 (WiFi, not OK), has 
dhcpcd.

The /etc/resolv.conf file is a real file, not a link to another file.

The article refers to  /etc/resolvconf/resolv.conf.d/head and 
/etc/resolvconf/resolv.conf.d/tail.  I don't have either of those files.

Adrian
-- 
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

[toc] | [prev] | [next] | [standalone]

#9468

On 8/21/2015 12:42, Adrian wrote:
> ps -A | grep -i dhc
>
> gives me different answers on different machines.  The Pi B+ (which is
> OK and on Ethernet) gives dhclient, whereas the Pi 2 (WiFi, not OK), has
> dhcpcd.
> Adrian

On the Pi running dhclient you set the DNS servers in 
/etc/network/interfaces.  On the Pi running dhcpcd you set the DNS 
servers in /etc/dhcpcd.conf.  But this is only for static addresses. 
For DHCP addresses, your router will supply your DHCP address and the 
DNS server address.  In any case you don't edit resolv.conf.

-- 

Knute Johnson

[toc] | [prev] | [next] | [standalone]

#9474

In message <mr90mg$oqf$1@dont-email.me>, Knute Johnson 
<nospam@rabbitbrush.frazmtn.com> writes
>On 8/21/2015 12:42, Adrian wrote:
>> ps -A | grep -i dhc
>>
>> gives me different answers on different machines.  The Pi B+ (which is
>> OK and on Ethernet) gives dhclient, whereas the Pi 2 (WiFi, not OK), has
>> dhcpcd.
>> Adrian
>
>On the Pi running dhclient you set the DNS servers in 
>/etc/network/interfaces.  On the Pi running dhcpcd you set the DNS 
>servers in /etc/dhcpcd.conf.  But this is only for static addresses. 
>For DHCP addresses, your router will supply your DHCP address and the 
>DNS server address.  In any case you don't edit resolv.conf.
>

Neither Pi has static addresses set, but the router (same router for 
both Pis) is set to always allocate the same IP address.


Adrian
-- 
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

[toc] | [prev] | [next] | [standalone]

#9489

On 08/22/2015 21:42, Adrian wrote:
>
> Neither Pi has static addresses set, but the router (same router for
> both Pis) is set to always allocate the same IP address.

One IP address for each Pi I hope...
-- 
Torfinn Ingolfsen,
Norway

[toc] | [prev] | [next] | [standalone]

#9491

In message <mrd4vm$qap$1@dont-email.me>, Torfinn Ingolfsen 
<tingo@home.no> writes
>On 08/22/2015 21:42, Adrian wrote:
>>
>> Neither Pi has static addresses set, but the router (same router for
>> both Pis) is set to always allocate the same IP address.
>
>One IP address for each Pi I hope...

Yes.

Adrian
-- 
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

[toc] | [prev] | [next] | [standalone]

#9494

In article <dpa1PRUFAk2VFwfP@ku.gro.lloiff>,
Adrian  <bulleid@ffoil.org.uk> wrote:
>In message <mrd4vm$qap$1@dont-email.me>, Torfinn Ingolfsen 
><tingo@home.no> writes
>>On 08/22/2015 21:42, Adrian wrote:
>>>
>>> Neither Pi has static addresses set, but the router (same router for
>>> both Pis) is set to always allocate the same IP address.
>>
>>One IP address for each Pi I hope...
>
>Yes.

If you have an IPv6 infrastructure in place the raspbian rpis will
happily connect, even to an V6-only network, and will take the
mandatory three ip(v6) addresses from the RA and the localnet MAC.

It also does the right thing in a combined v4 and v6 network. This
Just Works, just as with a Mac, or for a Windows v7 or later installation.

A rpi is also a very good platform for being a v6 tunnel client
with ra service to the local network.

apt-get install aiccu-sixxs (and maybe the RA)

-- mrr

[toc] | [prev] | [next] | [standalone]

#9495

Op 24-08-15 om 10:42 schreef Morten Reistad:
> If you have an IPv6 infrastructure in place the raspbian rpis will
> happily connect, even to an V6-only network, and will take the
> mandatory three ip(v6) addresses from the RA and the localnet MAC.

Not enabled by default, or did that change? I can't imagine. To enable 
until the next reboot: "sudo modprobe ipv6". To enable permanently: 
"sudo nano /etc/modules" and add "ipv6" on a new line.

[toc] | [prev] | [next] | [standalone]

#9496

In article <55dadffc$0$23858$e4fe514c@news.xs4all.nl>,
A. Dumas <alexandre@dumas.fr.invalid> wrote:
>Op 24-08-15 om 10:42 schreef Morten Reistad:
>> If you have an IPv6 infrastructure in place the raspbian rpis will
>> happily connect, even to an V6-only network, and will take the
>> mandatory three ip(v6) addresses from the RA and the localnet MAC.
>
>Not enabled by default, or did that change? I can't imagine. To enable 
>until the next reboot: "sudo modprobe ipv6". To enable permanently: 
>"sudo nano /etc/modules" and add "ipv6" on a new line.


Indeed. 

But once the module is loaded you have v6 connectivity. I just
did with a new rpi.

You may have to do a bit of configuration to have a v6-only
nameserver, but it is fairly straightforward.

-- mrr

[toc] | [prev] | [next] | [standalone]

#9492

On 8/23/2015 11:57 AM, Torfinn Ingolfsen wrote:
> On 08/22/2015 21:42, Adrian wrote:
>>
>> Neither Pi has static addresses set, but the router (same router for
>> both Pis) is set to always allocate the same IP address.
>
> One IP address for each Pi I hope...
And do remember that the Ethernet device IP number should be different 
from the WiFi IP address on each PI.
I have configured my router to read the MAC address of both the WiFi and 
Ethernet on the Pi B+ then assign the WiFi as 192.168.2.4 and the 
Ethernet as 192.168.2.3. The same with the Pi 2 - WiFi 192.168.2.6 and 
wired Ethernet responds on 192.168.2.5. By engaging this assignment in 
my router it allows each Pi portability to a friends network as the RPi 
still asks to handshake an IP address assignment from DHCP, the Dynamic 
Host Control Protocol, helping prevent the disaster of two devices with 
identical IP addresses battling for each other for gibberish I/O, while 
making direct IP access on the home network consistent over time and 
easy to remember.

I tend to keep the low bandwidth control channels open constantly on 
16Kbps WiFi and open the temporarily  wide bandwidth user accounts on 
the 10/100Kbps, the better to serve movies with. Just because one can 
log on to each channel with multiple accounts, that doesn't prevent me 
from simultaneous log-ins to root on the Ethernet wire or log-ins to pi 
or other user accounts via WiFi, it's just a personal arrangement 
preference which keeps the differences aligned in my mind because both 
Ethernet and WiFi are simultaneously active. Keeping the WiFi channel 
open with a laptop PuTTY login to root which constantly reports the RPi 
status stream with the top command solved the problem I'd had with the 
router dropping the WiFi every day. When needed, I'll temporarily open a 
duplicate PuTTY root session for admin command line tasks also on the 
WiFi connection, while top is running in a dedicated PuTTY window on the 
laptop,

I'm just sayin', make sure your Ethernet and WiFi are each being 
assigned a unique IP address on each RPi.

-- 
   All ladders in the Temple of the Forbidden Eye have thirteen steps.
There are thirteen steps to the gallows, firing squad or any execution.
  The first step is denial...                           Don't be bamboozled:
        Secrets of the Temple of the Forbidden Eye revealed!
           Indiana Jones™ Discovers The Jewel of Power!
          visit —(o=8> http://disneywizard.com/ <8=o)— visit

[toc] | [prev] | [next] | [standalone]

#9505

DisneyWizard the Fantasmic! wrote:

>                                     ...     Keeping the WiFi channel
> open with a laptop PuTTY login to root which constantly reports the RPi
> status stream with the top command solved the problem I'd had with the
> router dropping the WiFi every day.

Can't you keep the WiFi channel open with a cron job on the Rpi that
generates some traffic over the wlan0 interface at regular intervals?

Running something like
   ping -c 1 -I wlan0 your_router_address_or_name >/dev/null 2>&1
should do the job. That would remove the dependency on the laptop
keeping the connection open all the time.

But -frankly speaking- why do you need the WiFi connection at all if
the Rpi can already be reached over a probably better ethernet
connection?

regards,

Kees.

-- 
Kees Theunissen

[toc] | [prev] | [next] | [standalone]

#9506

In message <55de7aae$0$23774$e4fe514c@news.xs4all.nl>, Kees Theunissen 
<theuniss@rijnh.nl> writes
>DisneyWizard the Fantasmic! wrote:
>
>>                                     ...     Keeping the WiFi channel
>> open with a laptop PuTTY login to root which constantly reports the RPi
>> status stream with the top command solved the problem I'd had with the
>> router dropping the WiFi every day.
>
>Can't you keep the WiFi channel open with a cron job on the Rpi that
>generates some traffic over the wlan0 interface at regular intervals?
>
>Running something like
>  ping -c 1 -I wlan0 your_router_address_or_name >/dev/null 2>&1
>should do the job. That would remove the dependency on the laptop
>keeping the connection open all the time.
>
>But -frankly speaking- why do you need the WiFi connection at all if
>the Rpi can already be reached over a probably better ethernet
>connection?
>
>regards,
>
>Kees.
>

Because the Ethernet connection isn't always reliable.

I've had problems with one of my Pis not coming online when it boots up. 
Opinions seem to vary as why the Ethernet connection doesn't come up. In 
the house it is fine, but when it is out in the garden, it is less than 
evens as to whether or not it work, some days it just won't play.  Today 
I put it on WiFi (with the Ethernet unplugged), so we'll see what that 
does over the coming weeks.

I've tried setting up a cron job that runs once a minute that sends a 
single ping to the router, but that won't always wake the Ethernet 
connection up.

Adrian
-- 
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

[toc] | [prev] | [next] | [standalone]

#9507

On 27-08-15 21:35, Adrian wrote:
> Because the Ethernet connection isn't always reliable.
>
> I've had problems with one of my Pis not coming online when it boots up.
> Opinions seem to vary as why the Ethernet connection doesn't come up. In
> the house it is fine, but when it is out in the garden, it is less than
> evens as to whether or not it work, some days it just won't play.

Same problem here with any Pi directly connected to a Fritzbox 760 
router oon LAN port 3. Often it's enough to dis/reconnect the ethernet 
cable to re-establish a connection but sometimes I need to flip the 
power for a hard reset.

No such problems when connected via a small LAN switch. It has been 
suggested that noise/grounding might be the cause and the Fritzbox can't 
cope. It's a shame because the switch is yet another always-on power plug.

[toc] | [prev] | [next] | [standalone]

#9509

In message <55e00ab7$0$23864$e4fe514c@news.xs4all.nl>
          "A. Dumas" <alexandre@dumas.fr.invalid> wrote:

> On 27-08-15 21:35, Adrian wrote:
> > Because the Ethernet connection isn't always reliable.
> > 
> > I've had problems with one of my Pis not coming online when it boots up.
> > Opinions seem to vary as why the Ethernet connection doesn't come up. In
> > the house it is fine, but when it is out in the garden, it is less than
> > evens as to whether or not it work, some days it just won't play.
> 
> Same problem here with any Pi directly connected to a Fritzbox 760  router
> oon LAN port 3. Often it's enough to dis/reconnect the ethernet  cable to
> re-establish a connection but sometimes I need to flip the  power for a
> hard reset.

x86 boxes sometimes have the LAN fail to start up properly, too.
I don't regard anything as being immune in principle.

> No such problems when connected via a small LAN switch. It has been 
> suggested that noise/grounding might be the cause and the Fritzbox can't 
> cope. It's a shame because the switch is yet another always-on power plug.

Noise and grounding are often blamed when nothing can be proved.  I've
yet to find a case where noise and/or grounding really were the cause,
though.

Ethernet is always transformer coupled at both ends, which gives
excellent noise immunity and does not place any requirement on
earthing.

Dave

[toc] | [prev] | [next] | [standalone]

#9515

On Fri, 21 Aug 2015 20:42:35 +0100, Adrian wrote:

> In message <d3p1vmFk0ffU12@mid.individual.net>, ray carter
> <ray@zianet.com> writes
>>On Fri, 21 Aug 2015 17:01:26 +0100, Adrian wrote:
>>
>>> I'm having "fun" with a Pi 2 when it is using WiFi rather than
>>> Ethernet.
>>>
>>>
>>> On Ethernet, it appears to boot up, and pick up the time server OK,
>>> but on WiFi, it doesn't.  Doing some digging around on line, the
>>> suggestions seem to centre on making sure that the /etc/resolv.conf
>>> file has name servers in it.
>>>
>>> I've edited the file to put in a number of entries (cut and paste from
>>> a Pi B+), and the Pi 2 picks up the time server, and away we go.  As
>>> soon as I reboot, we are back to the same problem.  It seems that
>>> either the shutdown or the boot operation empties the file and puts :
>>>
>>> # Generated by resolvconf
>>>
>>> in the file instead, which is starting to get annoying.
>>>
>>> Strangely, the Pi 2 has a /etc/resolv.conf and a /etc/resolvconf.conf
>>> file, whereas the B+ only has the former.  Should I get rid of the
>>> latter file ?
>>>
>>> Both machines are running raspbian.
>>>
>>> Adrian
>>
>>Does this help:
>>
>>http://unix.stackexchange.com/questions/216774/keep-losing-resolv-conf-
>>configurations
> 
> Thanks, sort of.
> 
> ps -A | grep -i dhc
> 
> gives me different answers on different machines.  The Pi B+ (which is
> OK and on Ethernet) gives dhclient, whereas the Pi 2 (WiFi, not OK), has
> dhcpcd.
> 
> The /etc/resolv.conf file is a real file, not a link to another file.
> 
> The article refers to  /etc/resolvconf/resolv.conf.d/head and
> /etc/resolvconf/resolv.conf.d/tail.  I don't have either of those files.
> 
> Adrian

Noted that you have already solved the problem.

The article seems to give two routes:

"With resolvconf, if you want entries to be present only when a particular 
interface is active, add a dns-nameservers line to the corresponding 
stanza in /etc/network/interfaces."

Which is what I think you have done.

"With resolvconf, if you want entries to be present all the time, add them 
to /etc/resolvconf/resolv.conf.d/head or /etc/resolvconf/resolv.conf.d/
tail, depending on whether you want them to be first or last."

I note that these files are not present.
I think that all you need to do is create one or the other and they will 
be picked up.

I still don't quite understand why, if you are connecting to the same 
local router using either Ethernet or WiFi and using the router as your 
DHCP server in both cases, why you are not being given the same DNS Server 
configuration.

If it was a lack of name servers then you wouldn't be able to resolve 
anything - there should be nothing special about resolving the name of a 
time server as opposed to a web site or mail server.

It might be worth comparing the information in /etc/network/interfaces to 
see if there is something strange about your WiFi configuration as opposed 
to your Ethernet configuration.

Cheers

Dave R



-- 
Windows 8.1 on PCSpecialist box

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.sys.raspberry-pi

csiph-web