From: "JA Magallón" <jamagallon@ono.com>
To: autofs@linux.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: autofs does not resolve names ?
Date: Sat, 16 Jul 2011 03:01:41 +0200 [thread overview]
Message-ID: <20110716030141.3e6916e3@werewolf.home> (raw)
Hi all...
Since the update to autofs-5.0.6, I have a curious problem. Probably it is not autofs
to blame, but I ask here to see if someone can give me some light...
Setup:
/etc/autofs/auto.master:
/home ldap://danae-nfs.cps.unizar.es/automountMapName=auto_home,o=diis --timeout=60,tcp,nobrowse
(user homes map from LDAP, shared homes at a server)
The name is resolved:
annwn:/etc/autofs# host danae-nfs
danae-nfs.cps.unizar.es has address 155.210.152.202
annwn:/etc/autofs# ping danae-nfs
PING danae-nfs.cps.unizar.es (155.210.152.202) 56(84) bytes of data.
64 bytes from danae-nfs.cps.unizar.es (155.210.152.202): icmp_req=1 ttl=255 time=0.339 ms
...
But when I access home (ssh the box):
Jul 15 01:39:31 annwn automount[7774]: Starting automounter version 5.0.6, master map auto.master
Jul 15 01:39:31 annwn automount[7774]: using kernel protocol version 5.02
Jul 15 01:39:31 annwn automount[7774]: lookup_nss_read_master: reading master files auto.master
...
Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
Jul 15 01:39:31 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto udp version 0x30
Jul 15 01:39:37 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto tcp version 0x30
Where the hell does it get that IP address for my server ????
Diggin a bit more:
annwn:/var/log# host 69.65.19.116
116.19.65.69.in-addr.arpa domain name pointer nx-deleted-host-1.no-ip.com
because I have at /etc/resolv.conf:
search cps.unizar.es unizar.es no-ip.org
Why did it not resolved first with the first domain ?
If I delete the no-ip.org domain, I get:
Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
Jul 15 01:47:20 annwn automount[8068]: add_host_addrs: hostname lookup failed: Name or service not known
Jul 15 01:47:20 annwn automount[8068]: mount(nfs): no hosts available
Jul 15 01:47:20 annwn automount[8068]: dev_ioctl_send_fail: token = 28
Jul 15 01:47:20 annwn automount[8068]: failed to mount /home/magallon
automount does not add the search domains and resolve ? what am I doing wrong ?
is it a bug ? uuhhh ?
TIA
--
J.A. Magallon <jamagallon()ono!com> \ Winter is coming...
next reply other threads:[~2011-07-16 1:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 1:01 JA Magallón [this message]
2011-07-16 2:30 ` [autofs] autofs does not resolve names ? Ian Kent
2011-07-16 23:17 ` JA Magallón
2011-07-16 23:37 ` [autofs] " JA Magallón
2011-07-18 1:57 ` Ian Kent
2011-07-16 13:01 ` Frank Thommen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110716030141.3e6916e3@werewolf.home \
--to=jamagallon@ono.com \
--cc=autofs@linux.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).