getting nfs to work with short machine names and dns before files

2007-12-25 9:07:00

        well, i received three responses, all of which suggested making

sure that /etc/hosts had fqdn listings first, and one of which suggested

putting files before dns, which was a response that i had specifically

said i didn't want. the fqdn-in-/etc/hosts suggestion wasn't much help

either, since i already have fqdns listed (as the first entry for each ip)

in that file, and since (as i said in my question) /etc/hosts isn't even

being consulted, since dns is returning a valid response. (no one had

any suggestions about the parenthetical question about [SUCCESS=continue].)

        looks like i'll just use fqdns in dfstab, as well.

        -- sweth.

On Thu, Dec 24, 1998 at 05:27:56PM -0500, Sweth Chandramouli wrote:

> i've got an nfs server, whose /etc/nsswitch.conf has the line

> "hosts: files dns", whose /etc/hosts has a short (non-fqdn) alias for

> another machine, and whose /etc/dfs/dfstab has a share command that uses

> that same short (non-fqdn) alias. if i change nsswitch.conf to read

> "hosts: dns files", mounting from that other machine stops working. from

> what i can tell, nfs gets the mount request from the client, and sends

> a dns query for the ip from which it is getting the request; since that

> query returns an fqdn, which doesn't match the short entry in dfstab,

> the request is denied, without ever failing over to /etc/hosts. is there

> some way to cause nfs to, once the dns-returned entry fails to match,

> check /etc/hosts and see if a mapping listed there might match instead?

> please don't tell me to use fqdns in dfstab, or switch back to

> files before dns in nsswitch; if necessary, i'll do the former, but i'd

> really like to get things to work without either of those options.

>

> (on a related note, how does nsswitch.conf deal with a clause like

> [SUCCESS=continue] after an entry? that is, would "hosts: dns

> [SUCCESS=continue] files" act just like "hosts: files", or would it cache

> the result of the dns query, and then move on to files regardless, falling

> back to the dns results if nothing were found in files, so that it would

> act like "hosts: files dns" but with the added overhead of _having_ to do

> a dns query for every check?)

>

> tia,

> sweth.

>

>

> --

> Sweth Chandramouli

> IS Coordinator, The George Washington University

> <sweth@gwu.edu> / (202) 994 - 8521 (V) / (202) 994 - 0458 (F)

> *


--
Sweth Chandramouli
IS Coordinator, The George Washington University
<sweth@gwu.edu> / (202) 994 - 8521 (V) / (202) 994 - 0458 (F)
<a href="http://astaroth.nit.gwu.edu/~sweth/disc.html">*</a>

Comments

Got something to say?

You must be logged in to post a comment.