Bug 65639 - NFS allways use DNS for client verfication
Summary: NFS allways use DNS for client verfication
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Pete Zaitcev
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-29 10:59 UTC by Anders Damm
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-05-13 17:39:21 UTC
Embargoed:


Attachments (Terms of Use)

Description Anders Damm 2002-05-29 10:59:05 UTC
From Bugzilla Helper: 
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.0.0-10; Linux) 
 
Description of problem: 
A share that is exported with a IP-address/subnet mask shuld not be validatet against DNS, 
acording to the dokumentation.  
However, if the NFS-server is configured to use a DNS-server, a client validation is 
performed. 
This is a big problem i environment with bad DDNS (Microsoft 2000), where one or several 
reverse records will be returnd, and the mount request rejected.   
 
Version-Release number of selected component (if applicable): 
 
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1.Configer a Linux NFS server to use a well used W2k DDNS-server as DNS 
2.Export a NFS-sharem with IP-address/netmask e.g. 10.1.1.0/255.255.255.0 
3.Try to mount from a Linux client on the 10.1.1-network 
4.Configure the NFS-server not to use DNS, and it will work as expected 
  
 
Actual Results:  Mount denied 
 
Expected Results:  Mount ok 
 
Additional info:

Comment 1 Josh Wyatt 2002-09-25 19:55:02 UTC
Seeing the same thing here.  It appears that when hostnames are in /etc/exports,
knfsd feels the need to do reverse and forward dns lookups on the client.  in
win2k ddns situations, the forward lookup breaks, and the nfs server denies
access.

Here are two google groups messages showing more depth on the problem (beware of
wrapping...):
http://groups.google.com/groups?q=dns+group:mlist.nfs-valinux&hl=en&lr=&ie=UTF-8&selm=d430a976.0205072256.47e62042%40posting.google.com&rnum=1

http://groups.google.com/groups?q=dns+group:mlist.nfs-valinux&hl=en&lr=&ie=UTF-8&selm=nfs-valinux.1903F8F4F110D41192BA00805FFE09E40310347C%40exccyp-03.cyt.cpqcorp.net&rnum=5

Thanks,
josh


Comment 2 Josh Wyatt 2002-09-25 20:31:54 UTC
I should add that the server is running 7.2, the clients can be running anything
(we are using 7.3 on our clients).
Thanks,
Josh

Comment 3 Pete Zaitcev 2005-05-13 17:39:21 UTC
I think this bug was lost. Anders, if this is still a problem, please
file a new one, SteveD will take good care of NFS issues.



Note You need to log in before you can comment on or make changes to this bug.