I've noticed that /etc/resolv.conf seems to accumulate obsolete,
useless info as my laptop moves from one network to another. It looks
like dhcpcd adds stuff when a connection comes up, but never removes
it when the connection goes down.
There are search entries and nameserver entries from network
On 28/07/2014 16:34, Grand Duet wrote:
2014-07-28 1:00 GMT+03:00 Kerin Millar :
On 27/07/2014 21:38, Grand Duet wrote:
2014-07-27 22:13 GMT+03:00 Neil Bothwick :
On Sun, 27 Jul 2014 13:33:47 +0300, Grand Duet wrote:
That's what replaces it when eth0 comes up.
It looks like eth0 is not bein
2014-07-28 1:00 GMT+03:00 Kerin Millar :
> On 27/07/2014 21:38, Grand Duet wrote:
>>
>> 2014-07-27 22:13 GMT+03:00 Neil Bothwick :
>>>
>>> On Sun, 27 Jul 2014 13:33:47 +0300, Grand Duet wrote:
>>>
> That's what replaces it when eth0 comes up.
> It looks like eth0 is not being brought up ful
On 27/07/2014 21:38, Grand Duet wrote:
2014-07-27 22:13 GMT+03:00 Neil Bothwick :
On Sun, 27 Jul 2014 13:33:47 +0300, Grand Duet wrote:
That's what replaces it when eth0 comes up.
It looks like eth0 is not being brought up fully
It sounds logical. But how can I fix it?
By identifying how f
2014-07-27 23:28 GMT+03:00 Daniel Frey :
> On 07/27/2014 08:08 AM, Grand Duet wrote:
>>
>> If eth0 starts after lo, then I have the right /etc/resolv.conf
>> file, however if lo starts after eth0, then the DNS IPs in
>> resolv.conf file are overwritten with dummy instruction
>> for lo interface.
>>
2014-07-27 22:13 GMT+03:00 Neil Bothwick :
> On Sun, 27 Jul 2014 13:33:47 +0300, Grand Duet wrote:
>
>> > That's what replaces it when eth0 comes up.
>> > It looks like eth0 is not being brought up fully
>>
>> It sounds logical. But how can I fix it?
>
> By identifying how far it is getting and why
On 07/27/2014 08:08 AM, Grand Duet wrote:
>
> If eth0 starts after lo, then I have the right /etc/resolv.conf
> file, however if lo starts after eth0, then the DNS IPs in
> resolv.conf file are overwritten with dummy instruction
> for lo interface.
>
> But, now, after your suggestion, I have look
2014-07-27 21:14 GMT+03:00 Kerin Millar :
> On 27/07/2014 12:30, Grand Duet wrote:
>>
>> 2014-07-27 13:39 GMT+03:00 Walter Dnes :
>>>
>>> On Sun, Jul 27, 2014 at 12:21:23PM +0300, Grand Duet wrote
This is a continuation of the thread:
"Something went wrong with DNS, plz help!"
>
On Sun, 27 Jul 2014 13:33:47 +0300, Grand Duet wrote:
> > That's what replaces it when eth0 comes up.
> > It looks like eth0 is not being brought up fully
>
> It sounds logical. But how can I fix it?
By identifying how far it is getting and why no further. But it appears
that eth0 is being bro
On 27/07/2014 12:30, Grand Duet wrote:
2014-07-27 13:39 GMT+03:00 Walter Dnes :
On Sun, Jul 27, 2014 at 12:21:23PM +0300, Grand Duet wrote
This is a continuation of the thread:
"Something went wrong with DNS, plz help!"
Now, the issue became clearer, so I decided to start
a new thread with mor
> On Jul 27, 2014, at 16:39, Grand Duet wrote:
>
> 2014-07-27 16:10 GMT+03:00 Matti Nykyri :
>>> On Jul 27, 2014, at 13:33, Grand Duet wrote:
>>>
>>> 2014-07-27 12:29 GMT+03:00 Neil Bothwick :
> On Sun, 27 Jul 2014 12:21:23 +0300, Grand Duet wrote:
>
> In short: the contents of the
2014-07-27 17:50 GMT+03:00 Daniel Frey :
> On 07/27/2014 04:30 AM, Grand Duet wrote:
>>
>>> and also the output of the "rc-update show" command?
>>
>> # rc-update show
>> alsasound | boot
>>bootmisc | boot
>> dbus | default
>>
2014-07-27 14:30 GMT+03:00 Grand Duet :
> 2014-07-27 13:39 GMT+03:00 Walter Dnes :
>> On Sun, Jul 27, 2014 at 12:21:23PM +0300, Grand Duet wrote
>>> This is a continuation of the thread:
>>> "Something went wrong with DNS, plz help!"
>>>
>>> Now, the issue became clearer, so I decided to start
>>>
On 07/27/2014 04:30 AM, Grand Duet wrote:
>
>> and also the output of the "rc-update show" command?
>
> # rc-update show
> alsasound | boot
>bootmisc | boot
> dbus | default
> devfs | sysinit
>
2014-07-27 16:10 GMT+03:00 Matti Nykyri :
>> On Jul 27, 2014, at 13:33, Grand Duet wrote:
>>
>> 2014-07-27 12:29 GMT+03:00 Neil Bothwick :
On Sun, 27 Jul 2014 12:21:23 +0300, Grand Duet wrote:
In short: the contents of the file /etc/resolv.conf
is unpredictably different from o
> On Jul 27, 2014, at 13:33, Grand Duet wrote:
>
> 2014-07-27 12:29 GMT+03:00 Neil Bothwick :
>>> On Sun, 27 Jul 2014 12:21:23 +0300, Grand Duet wrote:
>>>
>>> In short: the contents of the file /etc/resolv.conf
>>> is unpredictably different from one reboot to another.
>>> It is either
>>> # G
2014-07-27 13:39 GMT+03:00 Walter Dnes :
> On Sun, Jul 27, 2014 at 12:21:23PM +0300, Grand Duet wrote
>> This is a continuation of the thread:
>> "Something went wrong with DNS, plz help!"
>>
>> Now, the issue became clearer, so I decided to start
>> a new thread with more descriptive Subject.
>>
>
Grand Duet wrote:
> 2014-07-27 12:29 GMT+03:00 Neil Bothwick :
> It sounds logical. But how can I fix it? Can carrier_timeout_eth0=
> setting in /etc/conf.d/net file help? If so, how much seconds should I
> use?
>> what do your logs say?
> Could you, please, be more precise where to look for "logs"
On Sun, Jul 27, 2014 at 12:21:23PM +0300, Grand Duet wrote
> This is a continuation of the thread:
> "Something went wrong with DNS, plz help!"
>
> Now, the issue became clearer, so I decided to start
> a new thread with more descriptive Subject.
>
> In short: the contents of the file /etc/resolv
2014-07-27 12:29 GMT+03:00 Neil Bothwick :
> On Sun, 27 Jul 2014 12:21:23 +0300, Grand Duet wrote:
>
>> In short: the contents of the file /etc/resolv.conf
>> is unpredictably different from one reboot to another.
>> It is either
>> # Generated by net-scripts for interface lo
>> domain mynetwor
On Sun, 27 Jul 2014 12:21:23 +0300, Grand Duet wrote:
> In short: the contents of the file /etc/resolv.conf
> is unpredictably different from one reboot to another.
> It is either
> # Generated by net-scripts for interface lo
> domain mynetwork
That's what you get when lo comes up.
> or
>
This is a continuation of the thread:
"Something went wrong with DNS, plz help!"
Now, the issue became clearer, so I decided to start
a new thread with more descriptive Subject.
In short: the contents of the file /etc/resolv.conf
is unpredictably different from one reboot to another.
It is either
Hi,
would you please be so kind not to hijack other threads.
Thanks...
Dirk
signature.asc
Description: This is a digitally signed message part.
Hi list,
I have VPN connection to private network with non-public
*.private.mydomain.tld.
*.private.mydomanin.tld has to be translated throu 1.2.4.3 and
everything else throu 2.3.4.5 , how to define that?
Thanks,
krasko
Daniel Pielmeier wrote:
I have access to my box now, did something like this work, instead of
setting dhcp_eth0="nodns".
config_eth0=( "dhcp" )
dns_servers_eth0=( "192.168.0.1" )
Thanks Daniel.
I have since discovered that myself. It seems odd that the
install instructions do not mention
Sean schrieb:
On a newly built amd64 based system my resolv.conf keeps getting
overwritten on system startup so I am loosing my nameserver entry.
The system is set with a static address and I have dhcp_eth0="nodns" in
my conf.d/net file.
I read that this included entry would prevent my resol
2007/12/10, Sean <[EMAIL PROTECTED]>:
> On a newly built amd64 based system my resolv.conf keeps
> getting overwritten on system startup so I am loosing my
> nameserver entry.
>
> The system is set with a static address and I have
> dhcp_eth0="nodns" in my conf.d/net file.
>
> I read that this incl
On a newly built amd64 based system my resolv.conf keeps
getting overwritten on system startup so I am loosing my
nameserver entry.
The system is set with a static address and I have
dhcp_eth0="nodns" in my conf.d/net file.
I read that this included entry would prevent my resolv.conf
file f
On 10:51 Fri 27 Oct , Matthew R. Lee wrote:
> Every time I boot my resolv.conf reverts to the original file with no name
> servers in it. Because I use my laptop in various places I have a series of
> resolv.conf files (resolv.conf.xx1, resolv.conf.xx2, etc) When I use a
> different networ
On Friday 27 October 2006 11:20, Novensiles divi Flamen wrote:
> Do you have 'dhcp_eth0="nodns" ' in your /etc/conf.d/net file? This problem
> came up recently with someone else, can't confirm whether it was the nodns
> option or a different one (possibly "notcp", which I can't find documented)
>
On Friday 27 October 2006 20:51, Matthew R. Lee wrote:
> Every time I boot my resolv.conf reverts to the original file with no name
> servers in it. Because I use my laptop in various places I have a series
> of resolv.conf files (resolv.conf.xx1, resolv.conf.xx2, etc) When I use a
> different ne
Every time I boot my resolv.conf reverts to the original file with no name
servers in it. Because I use my laptop in various places I have a series of
resolv.conf files (resolv.conf.xx1, resolv.conf.xx2, etc) When I use a
different network I just cp /etc/resolv.conf.xx1 /etc/resolv.conf Now I
32 matches
Mail list logo
