On 2010-08-06 10:01 +0200, Timo Juhani Lindfors wrote:
> With
>
> nfs:/home /home nfs defaults0 0
>
> in /etc/fstab I get
>
> mount.nfs: Failed to resolve server nfs: Temporary failure in name resolution
>
> on boot. This is because I use local bind9 and /etc/reso
On Fri, 06 Aug 2010 15:22:19 +0300, Timo Juhani Lindfors wrote:
> Camaleón writes:
>> So we are doing something wrong here.
>
> It seems that /etc/init.d/mountnfs.sh does not actually call mount, it
> is done by
>
> /etc/network/if-up.d/mountnfs
>
> when a network interface is brought up.
>
>
Timo Juhani Lindfors writes:
> Should I try starting bind9 before network is brought up? That sounds
> very counter-intuitive.
Replying to myself here: this fails since bind9 says "no networks
configured". A hack that works for now seems to be to add
if [ "$(pidof named)" = "" ]; then
/etc/i
Camaleón writes:
> So we are doing something wrong here.
It seems that /etc/init.d/mountnfs.sh does not actually call mount, it
is done by
/etc/network/if-up.d/mountnfs
when a network interface is brought up.
Should I try starting bind9 before network is brought up? That sounds
very counter-in
Camaleón writes:
> Did you read the manual or the docs for insserv? Maybe we are missing some
> step to fully populate the new boot sequence :-?
I did try but the man page does not really mention when symlinks are
created. For example
$ echo /etc/rc*/*bind9
/etc/rc0.d/K02bind9 /etc/rc1.d/K02bin
On Fri, 06 Aug 2010 12:52:11 +0300, Timo Juhani Lindfors wrote:
> Camaleón writes:
>> $named bind9
>
> Thanks for the effort but this does not seem to be enough:
>
> $ grep -Ev "(^#|^$)" /etc/insserv.conf
(...)
> $named +named +dnsmasq +lwresd bind9 $network
> $remote_fs
Camaleón writes:
> $namedbind9
Thanks for the effort but this does not seem to be enough:
$ grep -Ev "(^#|^$)" /etc/insserv.conf
$local_fs +mountall +mountoverflowtmp +umountfs
$network+networking +ifupdown
$named +named +dnsmasq +lwresd bind9 $network
$remote_fs
On Fri, 06 Aug 2010 11:01:01 +0300, Timo Juhani Lindfors wrote:
(...)
> I tried adding " bind9" to the $remote_fs line of /etc/insserv.conf but
> got
>
> $ sudo insserv --dryrun
> insserv: There is a loop between service bind9 and rsyslog if started
> insserv: loop involving service rsyslog at
With
nfs:/home /home nfs defaults0 0
in /etc/fstab I get
mount.nfs: Failed to resolve server nfs: Temporary failure in name resolution
on boot. This is because I use local bind9 and /etc/resolv.conf has
nameserver 127.0.0.1
I tried adding " bind9" to the $rem
guyren >> From: Guyren G Howe <[EMAIL PROTECTED]>
guyren >> Date: Wed, 22 Mar 2000 04:40:40 -0800
guyren >> To: "debian-user@lists.debian.org"
guyren >> Subject: DNS lookups fail
guyren >>
guyren >> I have somehow managed to get things so that the
try manually setting a DNS:
run nslookup
enter: server some.server.name (feel free to use mine ns1.firetrail.com or
ns2.firetrail.com)
then enter a domain or ip or something to query the server
if it times out it is more likely a network problem then a resolver
problem. if it works, then try yo
x27;s a routing
issue.
--
> From: Guyren G Howe <[EMAIL PROTECTED]>
> Date: Wed, 22 Mar 2000 04:40:40 -0800
> To: "debian-user@lists.debian.org"
> Subject: DNS lookups fail
>
> I have somehow managed to get things so that the computers going through my
>
I have somehow managed to get things so that the computers going through my
Debian 2.2 box for NAT can do DNS just fine, but I can't do a nslookup from
the same box itself to save myself.
nslookup never returns anything, even a timeout. My /etc/resolv.conf file
shows the same things I have set on
13 matches
Mail list logo
