Hi Andreas,
All the servers have the same /etc/resolv.conf file:
search our.domain.com
options ndots:2
nameserver ns0IP
nameserver ns1IP
I can't see any errors on the web servers or nfs servers referring a host
lookup failure.
Thanks
Simone
On 8/15/07, Andreas Rogge <[EMAIL PROTECTED]> wrote
Hi Simone,
what nameservers are configured for the nfs-servers?
Afaict the nfs-server does forward and reverse lookup the clients. So if
your nfs-server's DNS breaks (i.e. if only ns0 is configured there and
you shut down ns0) you might see the issue you described.
Regards,
Andreas
Simone s
Hi Peter
Thanks for your reply.
Some more info:
/etc/resolv.conf on ns1
nameserver ns0IP
nameserver ns1IP
At the time ns0 was down, I can see that even ns1 fails mounting the nfs
shares (timed out):
Aug 14 08:30:31 ns1 automount[4093]: >> mount: mount to NFS server 'nfs-web'
failed: timed out
The first thing that popped in my head was reverse lookup, but as I kept
reading and saw your test with web3 it could ave been a sync problem
between the two nameservers. By restarting ns1 all the zones were synced
again and your initial problem isn't there anymore and so your test with
web3 was su
Hi all,
Today we have had a strange problem that has taken down our website, we
understand what happened but not why so I am hoping someone has seen
this before.
We have our web servers (web1 web2 web3 . web10) mounting an NFS
share (/export/data) from server nfs1. On the web server side
5 matches
Mail list logo
