On Thu, 2010-01-07 at 16:31 +1030, Tim wrote:
Mikkel:
System -- Preferences -- Network Connections
Pick the type of interface, and then the specific interface.
Highlight it and click on edit.
Under the IPv4 Settings, change the Method drop-down to Automatic
(DHCP) address only. If
On Tue, 2010-01-05 at 21:30 -0500, Mail Lists wrote:
On 01/05/2010 10:08 AM, Patrick O'Callaghan wrote:
On Mon, 2010-01-04 at 19:08 -0600, Mikkel wrote:
On 01/04/2010 06:39 PM, Patrick O'Callaghan wrote:
I installed bind and tried to use it as a basic cacheing nameserver,
which in
On Tue, 2010-01-05 at 21:19 -0500, Tom Horsley wrote:
On Wed, 06 Jan 2010 00:26:00 +
Patrick O'Callaghan wrote:
It might, in fact it probably would, but it's hard to believe that that
is the way you're supposed to do this.
I'm sure it isn't, but it is easy and it works (except on
I've now rebooted to check, and /etc/resolv.conf has again been
overwritten by NM, despite the PEERDNS=no line in the ifcfg file, i.e.
it has reverted to what it was. NM seems to be calling dhclient with its
own private config file, the whereabouts of which are non-obvious.
Strange. You might
Mikkel:
System -- Preferences -- Network Connections
Pick the type of interface, and then the specific interface.
Highlight it and click on edit.
Under the IPv4 Settings, change the Method drop-down to Automatic
(DHCP) address only. If you are using IPv6, then change that
drop-down to
There's a suggestion that a resolv.conf.save file will be copied to
resolv.conf each reboot. You could try that file as a reset to (your)
normal options for your configuration.
--
[...@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replies to my address, the mailbox is
On Tue, 2010-01-05 at 00:39 +, Patrick O'Callaghan wrote:
I installed bind and tried to use it as a basic cacheing nameserver,
which in principal just means running named and
pointing /etc/resolv.conf to 127.0.0.1. However resolv.conf keeps
getting overwritten by NetworkManager,
Are you
On Tue, 2010-01-05 at 05:17 +0100, Tom H wrote:
How does one convince NM not to interfere with resolv.conf?
Don't know for sure how to make interfaces managed by NM
stop doing it, but for my non-NM system I still have to
prevent resolv.conf from being scrogged by setting
PEERDNS=no
On Tue, 05 Jan 2010 14:30:02 +
Patrick O'Callaghan wrote:
That seems to be working for the moment, but there's an element of magic
in it that makes me nervous. The default named.conf file is set up as a
simple cacheing nameserver for local queries, but where does named do
its recursive
On Tue, 2010-01-05 at 18:22 +1030, Tim wrote:
On Tue, 2010-01-05 at 00:39 +, Patrick O'Callaghan wrote:
I installed bind and tried to use it as a basic cacheing nameserver,
which in principal just means running named and
pointing /etc/resolv.conf to 127.0.0.1. However resolv.conf keeps
On Mon, 2010-01-04 at 19:08 -0600, Mikkel wrote:
On 01/04/2010 06:39 PM, Patrick O'Callaghan wrote:
I installed bind and tried to use it as a basic cacheing nameserver,
which in principal just means running named and
pointing /etc/resolv.conf to 127.0.0.1. However resolv.conf keeps
On Tue, 2010-01-05 at 09:54 -0500, Tom Horsley wrote:
On Tue, 05 Jan 2010 14:30:02 +
Patrick O'Callaghan wrote:
That seems to be working for the moment, but there's an element of magic
in it that makes me nervous. The default named.conf file is set up as a
simple cacheing nameserver
On Tue, 05 Jan 2010 15:24:00 +
Patrick O'Callaghan wrote:
There isn't. This is the default, unmodified named.conf.
So that probably means you are simply talking directly
to the root DNS servers and should be able to lookup
any public addresses. The problem you'd have with only
using
On Tue, 2010-01-05 at 15:24 +, Patrick O'Callaghan wrote:
On Tue, 2010-01-05 at 09:54 -0500, Tom Horsley wrote:
On Tue, 05 Jan 2010 14:30:02 +
Patrick O'Callaghan wrote:
That seems to be working for the moment, but there's an element of magic
in it that makes me nervous.
On 01/05/2010 09:08 AM, Patrick O'Callaghan wrote:
On Mon, 2010-01-04 at 19:08 -0600, Mikkel wrote:
System -- Preferences -- Network Connections
Pick the type of interface, and then the specific interface.
Highlight it and click on edit.
Under the IPv4 Settings, change the Method drop-down
On Tue, 2010-01-05 at 11:11 -0600, Mikkel wrote:
On 01/05/2010 09:08 AM, Patrick O'Callaghan wrote:
On Mon, 2010-01-04 at 19:08 -0600, Mikkel wrote:
System -- Preferences -- Network Connections
Pick the type of interface, and then the specific interface.
Highlight it and click on edit.
On Tue, 2010-01-05 at 11:07 -0500, Matthew Saltzman wrote:
On Tue, 2010-01-05 at 15:24 +, Patrick O'Callaghan wrote:
On Tue, 2010-01-05 at 09:54 -0500, Tom Horsley wrote:
On Tue, 05 Jan 2010 14:30:02 +
Patrick O'Callaghan wrote:
That seems to be working for the moment,
On Tue, 2010-01-05 at 10:59 -0500, Tom Horsley wrote:
On Tue, 05 Jan 2010 15:24:00 +
Patrick O'Callaghan wrote:
There isn't. This is the default, unmodified named.conf.
So that probably means you are simply talking directly
to the root DNS servers and should be able to lookup
any
On Wed, 06 Jan 2010 00:26:00 +
Patrick O'Callaghan wrote:
It might, in fact it probably would, but it's hard to believe that that
is the way you're supposed to do this.
I'm sure it isn't, but it is easy and it works (except on opensuse
where the whole boot process comes to a screeching
On 01/05/2010 10:08 AM, Patrick O'Callaghan wrote:
On Mon, 2010-01-04 at 19:08 -0600, Mikkel wrote:
On 01/04/2010 06:39 PM, Patrick O'Callaghan wrote:
I installed bind and tried to use it as a basic cacheing nameserver,
which in principal just means running named and
pointing /etc/resolv.conf
On Tue, 05 Jan 2010 00:39:26 +
Patrick O'Callaghan wrote:
How does one convince NM not to interfere with resolv.conf?
Don't know for sure how to make interfaces managed by NM
stop doing it, but for my non-NM system I still have to
prevent resolv.conf from being scrogged by setting
On 01/04/2010 06:39 PM, Patrick O'Callaghan wrote:
I installed bind and tried to use it as a basic cacheing nameserver,
which in principal just means running named and
pointing /etc/resolv.conf to 127.0.0.1. However resolv.conf keeps
getting overwritten by NetworkManager, and I notice an
How does one convince NM not to interfere with resolv.conf?
Don't know for sure how to make interfaces managed by NM
stop doing it, but for my non-NM system I still have to
prevent resolv.conf from being scrogged by setting
PEERDNS=no
in my /etc/sysconfig/network-scripts/ifcfg-eth0 file.
23 matches
Mail list logo
