On Wed, 31 Jul 2019 08:59:11 -0500
David Wright wrote:
> On Wed 31 Jul 2019 at 08:50:34 (-0400), Greg Wooledge wrote:
> > On Wed, Jul 31, 2019 at 09:21:32AM +0300, Reco wrote:
> > > On Wed, Jul 31, 2019 at 09:16:03AM +0300, Andrei POPESCU wrote:
> > > > On Mi, 31 iul 19, 09:06:36, Reco wrote:
> >
On Thu 01 Aug 2019 at 14:09:31 (-0400), Michael Stone wrote:
> On Thu, Aug 01, 2019 at 11:11:33AM -0500, David Wright wrote:
> > It surprised me that systemd doesn't just use something
> > like the gateway address if/when some address is absolutely
> > essential.
>
> Why on earth would it assum
Le 01/08/2019 à 20:06, Greg Wooledge a écrit :
On Thu, Aug 01, 2019 at 07:58:56PM +0200, Pascal Hambourg wrote:
Le 01/08/2019 à 18:18, David Wright a écrit :
I think that a lot of people install resolvconf (deliberately or
incidentally) without really understanding what it's for or what
it doe
ribute has
> > no effect if set on the symlink and will be reset at the next boot if
> > set on the target file in /run.
>
> Thinking twice and testing, it appears that you cannot even set file
> attributes in tmpfs nor on a symlink.
(which is why the wiki's first step i
Le 01/08/2019 à 19:58, Pascal Hambourg a écrit :
Le 01/08/2019 à 18:18, David Wright a écrit :
I think that a lot of people install resolvconf (deliberately or
incidentally) without really understanding what it's for or what
it does. Then, because most people naturally check the contents of
/et
On Thu, Aug 01, 2019 at 11:11:33AM -0500, David Wright wrote:
It surprised me that systemd doesn't just use something
like the gateway address if/when some address is absolutely
essential.
Why on earth would it assume that the gateway is running a resolver?
On Thu, Aug 01, 2019 at 07:58:56PM +0200, Pascal Hambourg wrote:
> Le 01/08/2019 à 18:18, David Wright a écrit :
> >
> > I think that a lot of people install resolvconf (deliberately or
> > incidentally) without really understanding what it's for or what
> > it does. Then, because most people natu
Le 01/08/2019 à 18:18, David Wright a écrit :
I think that a lot of people install resolvconf (deliberately or
incidentally) without really understanding what it's for or what
it does. Then, because most people naturally check the contents of
/etc/resolv.conf, they indulge in all sorts of cargo-
On 2019-08-01, Curt wrote:
> On 2019-07-31, Bob Bernstein wrote:
>> I _think_ my upgrade from Jessie to Stretch -- which entailed
>> installing systemd for the first time on this box -- introduced
>> that 8.8.8.8. into my config. I've never been at a loss to
>> select my own nameservers, and t
On Wed 31 Jul 2019 at 23:38:34 (+0200), Pascal Hambourg wrote:
> Le 31/07/2019 à 23:30, ghe a écrit :
> > On 7/31/19 2:52 PM, Pascal Hambourg wrote:
> >
> > > Without resolvconf, the DHCP client would have completely overwritten
> > > resolv.conf instead of just adding one line. With resolvconf, a
On Wed 31 Jul 2019 at 18:56:08 (-0400), Bob Bernstein wrote:
> I _think_ my upgrade from Jessie to Stretch -- which entailed
> installing systemd for the first time on this box -- introduced that
> 8.8.8.8. into my config. I've never been at a loss to select my own
> nameservers, and that never has
On 2019-07-31, Bob Bernstein wrote:
> I _think_ my upgrade from Jessie to Stretch -- which entailed
> installing systemd for the first time on this box -- introduced
> that 8.8.8.8. into my config. I've never been at a loss to
> select my own nameservers, and that never has been one of them.
>
I _think_ my upgrade from Jessie to Stretch -- which entailed
installing systemd for the first time on this box -- introduced
that 8.8.8.8. into my config. I've never been at a loss to
select my own nameservers, and that never has been one of them.
I was not even aware of that other file 'inte
Le 31/07/2019 à 23:30, ghe a écrit :
On 7/31/19 2:52 PM, Pascal Hambourg wrote:
Without resolvconf, the DHCP client would have completely overwritten
resolv.conf instead of just adding one line. With resolvconf, at least
you can have some control over resolv.conf.
OK. vi gives me all the cont
On 7/31/19 2:52 PM, Pascal Hambourg wrote:
> Without resolvconf, the DHCP client would have completely overwritten
> resolv.conf instead of just adding one line. With resolvconf, at least
> you can have some control over resolv.conf.
OK. vi gives me all the control I need over resolv.conf. I unde
Le 31/07/2019 à 21:44, ghe a écrit :
On 7/31/19 1:20 PM, Greg Wooledge wrote:
I still feel like you're missing the big picture here. resolvconf isn't
the thing that's modifying your /etc/resolv.conf file.
It's the thing (that was) modifying my resolv.conf.
Resolv
On Mi, 31 iul 19, 13:44:51, ghe wrote:
> On 7/31/19 1:20 PM, Greg Wooledge wrote:
>
> > I still feel like you're missing the big picture here. resolvconf isn't
> > the thing that's modifying your /etc/resolv.conf file.
>
> It's the thing (that
On Mi, 31 iul 19, 02:37:40, Bob Bernstein wrote:
> On Wed, 31 Jul 2019, Andrei POPESCU wrote:
>
> > It depends a lot on what combination of packages you have installed and
> > are using.
> >
> > Starting with the obvious ones, please show the output of:
>
> Ok. One dotted-four required obfuscati
On Mi, 31 iul 19, 08:59:11, David Wright wrote:
> On Wed 31 Jul 2019 at 08:50:34 (-0400), Greg Wooledge wrote:
> > On Wed, Jul 31, 2019 at 09:21:32AM +0300, Reco wrote:
> > > On Wed, Jul 31, 2019 at 09:16:03AM +0300, Andrei POPESCU wrote:
> > > > On Mi, 31 iul 19, 09:06:36, Reco wrote:
> > > > > As
On 7/31/19 1:20 PM, Greg Wooledge wrote:
> I still feel like you're missing the big picture here. resolvconf isn't
> the thing that's modifying your /etc/resolv.conf file.
It's the thing (that was) modifying my resolv.conf.
I have 2 Enet connections: a reliable T1
/etc. If it's still there.
I still feel like you're missing the big picture here. resolvconf isn't
the thing that's modifying your /etc/resolv.conf file. resolvconf is
a mitigating layer that's trying to take control over the *other*
entities which are trying to edit t
On 7/31/19 12:52 PM, Greg Wooledge wrote:
> Removing /etc/resolvconf sounds like terrible> advice.
> If you want to remove resolvconf, remove the> package with dpkg or apt.
> Don't just start removing random
configuration> files and directories
Good point, well taken.
I've always just deleted
On Wed, Jul 31, 2019 at 12:44:50PM -0600, ghe wrote:
> On 7/31/19 12:17 PM, Bob Bernstein wrote:
>
> > Sure enough, there it was, for eth0. I commented it out and added a line
> > for the nameserver I wanted, and bingo, we have lift off.
>
> That works, but if you want to specify the DNS server,
On 7/31/19 12:17 PM, Bob Bernstein wrote:
> Sure enough, there it was, for eth0. I commented it out and added a line
> for the nameserver I wanted, and bingo, we have lift off.
That works, but if you want to specify the DNS server, delete those 2
DNS lines in /etc...interfaces, and edit /etc/reso
Le 31/07/2019 à 19:56, Greg Wooledge a écrit :
On Wed, Jul 31, 2019 at 07:51:45PM +0200, Pascal Hambourg wrote:
Le 31/07/2019 à 17:10, Bob Bernstein a écrit :
What I want to do is get rid of the google 8.8.8.8 and replace it with a
static nameserver suggested by my vpn.
Edit /etc/network/int
SOLVED, I think.
After all the reading you guys gave me I sat pondering this
morning, and it dawned on me that if I looked at 'interfaces'
and found that darn 8.8.8.8 ip in there, that I might have the
clue I needed.
Sure enough, there it was, for eth0. I commented it out and
added a line f
On Wed, Jul 31, 2019 at 07:51:45PM +0200, Pascal Hambourg wrote:
> Le 31/07/2019 à 17:10, Bob Bernstein a écrit :
> >
> > What I want to do is get rid of the google 8.8.8.8 and replace it with a
> > static nameserver suggested by my vpn.
>
> Edit /etc/network/interfaces.
That isn't a full answer
Le 31/07/2019 à 17:10, Bob Bernstein a écrit :
What I want to do is get rid of the google 8.8.8.8 and replace it with a
static nameserver suggested by my vpn.
Edit /etc/network/interfaces.
Hi.
On Wed, Jul 31, 2019 at 11:10:32AM -0400, Bob Bernstein wrote:
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by r$
This simplifies things greatly
> What I want to do is get rid of the google 8.8.8.8 and replace it with a
> static nameserver suggested by my vpn.
ls
re/man/man1/resolvconf.1.gz
> >
> > tomas@trotzki:~$ dpkg -S resolv.conf
> > manpages: /usr/share/man/man5/resolv.conf.5.gz
>
> resolv.conf(5) is the configuration file for the DNS resolver in libc.
>
> resolvconf(8) is a Debian package that intercepts attempts by various
> o
ges: /usr/share/man/man5/resolv.conf.5.gz
resolv.conf(5) is the configuration file for the DNS resolver in libc.
resolvconf(8) is a Debian package that intercepts attempts by various
other packages to mangle your /etc/resolv.conf file, and lets you control
how they can or cannot do so.
resolvconf(1) is
On Wed, Jul 31, 2019 at 10:27:01AM -0400, Greg Wooledge wrote:
> On Wed, Jul 31, 2019 at 08:59:11AM -0500, David Wright wrote:
> > It might be the documentation that's confused. Here's an extract from
> > man resolvconf
> >
> >
> >
> >ifup
> >The ifup program can be used to c
I've begun a new thread to add some back-story to my "Which
resolv.conf file?" inquiry. *Thanks* to all who have chimed in.
nb. Judah: If "DE" means "desktop environment" then I don't
think I have one. I run the minimalist icewm, and I do not have
netwo
On Wed, Jul 31, 2019 at 10:27:01AM -0400, Greg Wooledge wrote:
> On Wed, Jul 31, 2019 at 08:59:11AM -0500, David Wright wrote:
> > It might be the documentation that's confused. Here's an extract from
> > man resolvconf
> >
> >
> >
> >ifup
> >The ifup program can be used to c
On Wed, Jul 31, 2019 at 08:59:11AM -0500, David Wright wrote:
> It might be the documentation that's confused. Here's an extract from
> man resolvconf
>
>
>
>ifup
>The ifup program can be used to configure network interfaces
[...]
Mine doesn't... wait, what...
wooledg:~$ d
On Wed 31 Jul 2019 at 08:50:34 (-0400), Greg Wooledge wrote:
> On Wed, Jul 31, 2019 at 09:21:32AM +0300, Reco wrote:
> > On Wed, Jul 31, 2019 at 09:16:03AM +0300, Andrei POPESCU wrote:
> > > On Mi, 31 iul 19, 09:06:36, Reco wrote:
> > > > Assuming it is, and you're using ifupdown, you need to chang
On Wed, Jul 31, 2019 at 09:21:32AM +0300, Reco wrote:
> On Wed, Jul 31, 2019 at 09:16:03AM +0300, Andrei POPESCU wrote:
> > On Mi, 31 iul 19, 09:06:36, Reco wrote:
> > > Assuming it is, and you're using ifupdown, you need to change
> > > "dns-nameserver" stanza in the interface definition.
> >
> >
On Wed, Jul 31, 2019 at 01:46:45AM -0400, Bob Bernstein wrote:
> I want to make a change or two to resolv.conf, but every time I come across
> it I flee in terror, warned that my changes will be destroyed and the linux
> gods angered.
>
> What is the approved method for changing the list of DNS se
On 2019-07-31, Bob Bernstein wrote:
> I want to make a change or two to resolv.conf, but every time I
> come across it I flee in terror, warned that my changes will be
> destroyed and the linux gods angered.
>
> What is the approved method for changing the list of DNS servers
> called upon by,
I use USB tethering and NetworkManager just creates a new wired connection
whenever I make changes to existing one and reconnect a phone. Also I may use
random WiFi spots from time to time and do not want to set up each of them.
The solution for me is:
[main]
dns=none
in /etc/NetworkManager/Ne
Assuming you're using a DE, make your desired changes in the GUI
network/connection settings and they'll get written to resolv.conf.
On Wed, Jul 31, 2019, 01:03 Bob Bernstein wrote:
> I want to make a change or two to resolv.conf, but every time I
> come across it I flee in terror, warned that m
Rather than try to control this on each machine, I have set up my
router, running OpenWRT, to serve the nameservers as part of the DHCP
configuration.
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Web: https://www.n0nb.us
On Wed, 31 Jul 2019, Andrei POPESCU wrote:
It depends a lot on what combination of packages you have installed and
are using.
Starting with the obvious ones, please show the output of:
Ok. One dotted-four required obfuscation in my humble
judgement. I hope I got your list correctly:
$ apt
Sorry! Switched machines and lost track of who I was!
-- Forwarded message --
From: Bob Bernstein
To: Debian User List
Subject: Re: Which resolv.conf file?
Date: Wed, 31 Jul 2019 02:37:40
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
On Wed, 31 Jul 2019, Andrei POPESCU wrote
Hi.
On Wed, Jul 31, 2019 at 09:16:03AM +0300, Andrei POPESCU wrote:
> On Mi, 31 iul 19, 09:06:36, Reco wrote:
> > On Wed, Jul 31, 2019 at 01:46:45AM -0400, Bob Bernstein wrote:
> > > I want to make a change or two to resolv.conf, but every time I come
> > > across it I flee in terror, warn
On Mi, 31 iul 19, 09:06:36, Reco wrote:
> Hi.
>
> On Wed, Jul 31, 2019 at 01:46:45AM -0400, Bob Bernstein wrote:
> > I want to make a change or two to resolv.conf, but every time I come
> > across it I flee in terror, warned that my changes will be destroyed
> > and the linux gods angered.
>
On Mi, 31 iul 19, 01:46:45, Bob Bernstein wrote:
> I want to make a change or two to resolv.conf, but every time I come across
> it I flee in terror, warned that my changes will be destroyed and the linux
> gods angered.
>
> What is the approved method for changing the list of DNS servers called u
Hi.
On Wed, Jul 31, 2019 at 01:46:45AM -0400, Bob Bernstein wrote:
> I want to make a change or two to resolv.conf, but every time I come
> across it I flee in terror, warned that my changes will be destroyed
> and the linux gods angered.
Have you meant this resolv.conf line?
# Dynamic r
I want to make a change or two to resolv.conf, but every time I
come across it I flee in terror, warned that my changes will be
destroyed and the linux gods angered.
What is the approved method for changing the list of DNS servers
called upon by, in my case, Stretch on amd-64?
(Is there some
On Sun, 08 May 2011 22:27:40 +0100, Lisi wrote:
> On Sunday 08 May 2011 18:49:27 Camaleón wrote:
>> Good. And I'm so sorry for NM but is nothing but a headache
>
> If NM ever gets installed by default, the first thing I do is purge it!
> ;-)
I don't like the idea of not having it installed.
Th
On Sunday 08 May 2011 18:49:27 Camaleón wrote:
> Good. And I'm so sorry for NM but is nothing but a headache
If NM ever gets installed by default, the first thing I do is purge it! ;-)
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble
On Sun, 08 May 2011 18:18:58 +0100, AG wrote:
> On 08/05/11 17:53, Camaleón wrote:
>>
>> Ensure:
>>
>> - There is a static "/etc/resolv.conf" file not pointing to nothing (if
>> not there, recreate one)
>
> Can you clarify this suggestion plea
in resolvconf (no description available)
If you look at the pipes and slashes you can tell what each character
means. In my case it's
Desired = Install
Status = Not
(hmm, this is curious, I'll have to investigate...)
Anyway, purged those using Brian's dpkg
On 08/05/11 17:53, Camaleón wrote:
Ensure:
- There is a static "/etc/resolv.conf" file not pointing to nothing (if
not there, recreate one)
Can you clarify this suggestion please. Do you mean that the
/etc/resolv.conf must *not* be pointing to something or *must* be
pointing to
I'll have to investigate...)
> Anyway, purged those using Brian's dpkg method rebooted ... and
> still no resolv.conf file.
>
> So, Hans suggested that I delete the symlink to resolvconf, but
> resolvconf isn't installed. However, since its config files are
> ther
xplain and remedy why the
> /etc/resolv.conf file is being erased at shutdown/ reboot. It is
> definitely this file that is the critical piece here, because when ever
> I repopulate the file connectivity is restored. How do I keep that file
> immutable? Will changing permissi
t;
>> would remove the config files too.
>>
>>
> Thanks all - learn something everyday: didn't know that is what rc
> referred to.
>
> Anyway, purged those using Brian's dpkg method rebooted ... and still no
> resolv.conf file.
Ensure:
- There is a static &qu
lled.
rc - Package removed but configuration files remain.
dpkg --purge resolvconf
would remove the config files too.
Thanks all - learn something everyday: didn't know that is what rc
referred to.
Anyway, purged those using Brian's dpkg method rebooted ... and still no
resolv.co
Camaleón wrote:
dpkg -l | grep resolvconf
rc resolvconf
1.48 name server information handler
Ein? >>>:-)
So you finally do have it installed.
Remember that this package can be also interferring with your "/etc/
resolv.conf" file so eith
ou finally do have it installed.
>>
>> Remember that this package can be also interferring with your "/etc/
>> resolv.conf" file so either you configure it properly or you remove it.
>> Choose your poison :-)
> And yet ...
>
> $ sudo apt-get remove --purge res
On Sun 08 May 2011 at 13:29:19 +, Camaleón wrote:
> On Sun, 08 May 2011 13:30:59 +0100, AG wrote:
>
> > dpkg -l | grep resolvconf
> > rc resolvconf
> > 1.48 name server information handler
>
> Ein? >>>:-)
>
> So you finally do have it installed.
rc - Package r
y do have it installed.
Remember that this package can be also interferring with your "/etc/
resolv.conf" file so either you configure it properly or you remove it.
Choose your poison :-)
And yet ...
$ sudo apt-get remove --purge resolvconf
Reading package lists... Done
Building depe
name server information handler
Ein? >>>:-)
So you finally do have it installed.
Remember that this package can be also interferring with your "/etc/
resolv.conf" file so either you configure it properly or you remove it.
Choose your poison :-)
Gr
On 08/05/11 11:55, Brian wrote:
On Sun 08 May 2011 at 10:34:00 +0100, AG wrote:
But, after rebooting this file was again blank, stopping me from
accessing the Net. How can I ensure that this file remains populated
between reboots? Or does this file get generated by some other
function, and in
On Sun 08 May 2011 at 10:34:00 +0100, AG wrote:
> But, after rebooting this file was again blank, stopping me from
> accessing the Net. How can I ensure that this file remains populated
> between reboots? Or does this file get generated by some other
> function, and in which case, what?
Wh
Further developments on this:
When I rebooted after the installation, I lost my ability to access the
Net (again). I checked the contents of /etc/resolv.conf and there was
nothing in that file - apparently it is generated by Network Manager, so
I reinstalled Network Manager and manually copie
jdaues writes:
> All my internet connections are working now, thanks to resolvconf (and
> to Jhair)
Good to know :)
Have fun,
--
-- Jhair
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
All my internet connections are working now, thanks to resolvconf (and
to Jhair)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
package acts like a refferee when different packages want
to change /etc/resolv.conf at different times. It notes what each
package tries to do so that when the package undoes what it thought it
did, you're left with an accurate resolv.conf file.
My Etch installer put the resolvconf hook
On Wed, Jan 10, 2007 at 05:48:47PM -0600, John Hasler wrote:
> If you have the zeroconf package installed, remove it. Remove resolvconf
> as well. You don't need it.
to clarify... if youhave the zeroconf package that is probably what is
over-riding your resolv.conf. if you also remove resolvconf
If you have the zeroconf package installed, remove it. Remove resolvconf
as well. You don't need it.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
jdaues writes:
> I read the man page. it gives no hint as to the syntax. I see nothing
> on the internets about this either. I can only guess maybe this:
> domain 123.45.67.8 91.23.456.78
> or
> dns 123.45.67.8 91.23.456.78
> Are either of these correct?
The syntax is the same as the one desc
I read the man page. it gives no hint as to the syntax. I see nothing
on the internets about this either. I can only guess maybe this:
domain 123.45.67.8 91.23.456.78
or
dns 123.45.67.8 91.23.456.78
Are either of these correct?
Jhair Tocancipa Triana wrote:
jdaues writes:
So I installed
jdaues writes:
> So I installed resolvconf, and then reentered the values for the
> network. I rebooted and now resolv.conf is this:
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
> resolvconf(8)
> #DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> Ther
in the resolvconf README file.
What is this telling me?
Jhair Tocancipa Triana wrote:
jdaues writes:
The etc/resolv.conf file is being written over when i reboot.
I have setup for static ip address, NOT dhcp. The outside word sees
the static ip address, and inside on the NAT, each machine is
jdaues writes:
> The etc/resolv.conf file is being written over when i reboot.
> I have setup for static ip address, NOT dhcp. The outside word sees
> the static ip address, and inside on the NAT, each machine is
> 192.168.0.x. In KDE, System -> Networking, I set up the ip ad
The etc/resolv.conf file is being written over when i reboot.
I have setup for static ip address, NOT dhcp. The outside word sees the
static ip address, and inside on the NAT, each machine is 192.168.0.x.
In KDE, System -> Networking, I set up the ip address, subnet mask,
gateway addr
g /000 disappear from your /etc/resolv.conf file.
I missed the original post. But that problem can also be resolved by
upgrading from the old dhcp version 2 to the newer dhcp version 3.
apt-get install dhcp3-client
Bob
pgp0.pgp
Description: PGP signature
This problem can also be resolved using dhclient by putting the following
into your /etc/dhclient.conf file
supersede domain-name "[yourdomain.com]"
You then can run dhclient again to renew your lease and you will see the
trailing /000 disappear from your /etc/resolv.conf fil
www.cpqlinux.com/sitemap.html
This email is in regards to:
http://lists.debian.org/debian-user/2003/debian-user-200308/msg05196.html
On Thu, 2003-08-28 at 13:06, Victory wrote:
I setup my machine as a dhcp client, once in a while
it add 000 to the end of search entry in "resolv.conf" file
i.
On Thu, Aug 28, 2003 at 02:06:57PM -0400, Victory wrote:
| I setup my machine as a dhcp client, once in a while
| it add 000 to the end of search entry in "resolv.conf" file
| i.e "search mydomain.com\000" and it causing machine can not
| ping other machine by name,
| Where
On Thu, 2003-08-28 at 13:06, Victory wrote:
> I setup my machine as a dhcp client, once in a while
> it add 000 to the end of search entry in "resolv.conf" file
> i.e "search mydomain.com\000" and it causing machine can not
> ping other machine by name,
> Wher
I setup my machine as a dhcp client, once in a while
it add 000 to the end of search entry in "resolv.conf" file
i.e "search mydomain.com\000" and it causing machine can not
ping other machine by name,
Where're these number 000 come from and how do to protect it
from do
83 matches
Mail list logo
