New DNS, NFS stops working.

[Steve Huizenga]

I built a new DNS server, made all my PCs and HPs use it. When I unplugged my old DNS server from the network all my PC NFS clients and my HP 10.20 NFS clients could not mount any exported directories. I can find no reference to the old DNS server anywhere. What am I missing?

[Michael Elleby III_1]

Hello-

On your nfs clients, issue a showmount -e 'servername' and see if the export dirs show up.

If not, then I'd suggest going back to your nfs servers and issuing an exportfs -a command, after you have reviewed the /etc/exports file.

Also, do your clients know about the new DNS in the 'neighborhood' and does he know about them? Some nslookups could help to answer this..

just my .02 worth..

HTH,

Mike-

[steven Burgess_2]

Hi

From the machines you are attempting to mount the exported filesystem , can you succesfully lookup the remote host ?

What type of error messages are you receiving when the mount is attempted ?

Does the new DNS server have the same ip address ?

HTH

Steve

[Jeff Schussele]

Hi Steve,

Seen it before....

Does the new DNS server have an entry for itself?
Forward AND reverse?

Rgds,
Jeff

[Steve Huizenga]

Steven,

The new DNS server has a new IP address.
Nslookups all work as expected. It seems like the NFS server is not "authenticating(?)" the client like the IPs don't match the names. Also, on 10.20 client when the old DNS is disconnected I can't fully login even from the console. It seems to hang on the .profile.

Steve

[Bernhard Mueller]

Hi,

if you changed the domain name you need to restart rpc.mountd on the NFS clients

Regards,
Bernhard

[U.SivaKumar_2]

Hi,

If you have used DNS hostnames for NFS access authentication . Then have you created reverse DNS records for the NFS clients for connecting to the NFS server.

In other words , given a clients IP address the NFS server should be able to resolve the DNS name of the client. Then only it can allow the trusted client .

regards,
U.SivaKumar