Jack,
Thank you for this tip (and also to Mark), switching off peerdns
seems to have done the trick.
Best regards,
Graeme.
--
Graeme J Hosking
pgp0.pgp
Description: PGP signature
First up disable a package called "tmdns" for some reason it's enabled
by default.. don't actually remove the package, as every time you
configure your network with drakconf, drakconf will reinstall the
package..
The commands to disable it..
"service tmdns stop"
"chkconfig --del tndns"
Next
http://www.monkeynoodle.org/comp/reply-to/
[EMAIL PROTECTED] jack]$ cat /etc/sysconfig/network
NETWORKING=yes
FORWARD_IPV4=false
DHCP_HOSTNAME=chupacabra.monkeynoodle.org
HOSTNAME=chupacabra.monkeynoodle.org
DOMAINNAME=monkeynoodle.org
PEERDNS=yes
DHCP_TIMEOUT=5
peerdns does what you want. That d
Hi,
I wonder if someone can tell me how to prevent the contents of my
/etc/resolv.conf from being re-written every time my NIC is brought
up? Or at least, allow me to keep entries in that file that I have
put there manually.
Basically, the NIC connected to my cable modem has to use DHCP
At 12.12 21/08/2003, you wrote:
As I understand it, zeroconf is sposed to be to linux what netbeui is to
windoze
or what appletalk is to macs.
Well, zeroconf is supposed to be what RendezVous is for macs X... they are
the same thing (and it was born in Apple)...
A quick google search shows that i
[mailto:[EMAIL PROTECTED] Behalf Of Jim C
>Sent: Thursday, 21 August 2003 4:22 AM
>To: [EMAIL PROTECTED]
>Subject: Re: [expert] resolv.conf
>
>
>
>>Just a quick note on this.. I find it better to run the command
>>"service tmdns stop" then "chkconfig --
On Wednesday 20 August 2003 02:29 pm, James Sparenberg wrote:
> What it is, is a re-implementation of Novel Network. And is supposed to
> be (according the the website I was directed to by someone) in very
> alpha form. As for the why. After watching the list on 9.1, I got the
> feeling that the
On Wed, 20 Aug 2003 13:21:48 -0700
Jim C <[EMAIL PROTECTED]> wrote:
> I'll second this. I sure would like to know what it is good for. It
> must be good for something.
And Why was it necessary to make it as the default in All network
set-ups?
Charles
--
Be careful how you get yourself
Just a quick note on this.. I find it better to run the command
"service tmdns stop" then "chkconfig --del tmdns" as if tmdns was
removed with "rpm -e" it gets installed and enabled again, when one
configures their network with drakconf.. It's just better to switch it
off.. When it is just swi
On Wed, 2003-08-20 at 04:17, Bryan Phinney wrote:
> On Tuesday 19 August 2003 09:36 pm, James Sparenberg wrote:
>
> > Dirty fix chmod /etc/resolv.conf to 444 (read only) and see what it
> > is that "complains" when it can't write to the file.
> Thanks all, I found the solution. It turns out t
On Wednesday 20 August 2003 11:31 am, Mark Williamson wrote:
> Just a quick note on this.. I find it better to run the command
> "service tmdns stop" then "chkconfig --del tmdns" as if tmdns was
> removed with "rpm -e" it gets installed and enabled again, when one
> configures their network wit
On Wed, 2003-08-20 at 08:31, Mark Williamson wrote:
> On Wed, 2003-08-20 at 14:35, Todd Lyons wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Bryan Phinney wanted us to know:
> >
> > >I am having problems getting SA to do the rbl checks. It appears that my
> > >/etc/resolv.
On Wed, 2003-08-20 at 14:35, Todd Lyons wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bryan Phinney wanted us to know:
>
> >I am having problems getting SA to do the rbl checks. It appears that my
> >/etc/resolv.conf file keeps getting built with 127.0.0.1 as the first name
> >s
On Tuesday 19 August 2003 09:36 pm, James Sparenberg wrote:
> Dirty fix chmod /etc/resolv.conf to 444 (read only) and see what it
> is that "complains" when it can't write to the file.
Thanks all, I found the solution. It turns out that the tmdns stuff that
Mandrake loads for zeroconf is the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bryan Phinney wanted us to know:
>I am having problems getting SA to do the rbl checks. It appears that my
>/etc/resolv.conf file keeps getting built with 127.0.0.1 as the first name
>server. Other network utilities appear to be able to bypass thi
On Tue, 2003-08-19 at 16:37, Rolf Pedersen wrote:
> Bryan Phinney wrote:
> > I am having problems getting SA to do the rbl checks. It appears that my
> > /etc/resolv.conf file keeps getting built with 127.0.0.1 as the first name
> > server. Other network utilities appear to be able to bypass th
Bryan Phinney wrote:
I am having problems getting SA to do the rbl checks. It appears that my
/etc/resolv.conf file keeps getting built with 127.0.0.1 as the first name
server. Other network utilities appear to be able to bypass this and try
each nameserver before giving up but the Net::DNS pe
I am having problems getting SA to do the rbl checks. It appears that my
/etc/resolv.conf file keeps getting built with 127.0.0.1 as the first name
server. Other network utilities appear to be able to bypass this and try
each nameserver before giving up but the Net::DNS perl module is not that
18 matches
Mail list logo
