Urgent Help needed

[Andy Bradford]

Thus said Stephen Smith on Tue, 06 Jun 2006 12:20:45 MDT:

> <date/time> orasrv rpc.mountd: refused  mount request from 192.168.1.5
> (luke.168.192.in-addr.arpa)  for  /data3/qcdm  (/data3/qcdm):  no  DNS
> forward lookup

Hmm, seems like 192.168.1.5 has a PTR of luke.168.192.in-addr.arpa eh?

> To me this shows forward resolution is working.

You aren't checking the right forward resolution...

> ;;ANSWER SECTION:
> 5.1.168.192.in-addr.arpa.  86400     IN        PTR        
> luke.168.192.in-addr.arpa.

Cool, so  now what does  an A record for  luke.168.192.in-addr.arpa look
like:

dig luke.168.192.in-addr.arpa

> If I understand dig, this show reverse resolution working as well.

Yes, the PTR resolved just fine, but how about the forward of that PTR?

> Can anyone help  me resolve this issue.  I'm running in the  "I hope I
> don't  have to  reboot" mode,  otherwise I  will loose  all of  my nfs
> shares between all computers in my server farm.

Not likely, however your DNS is misconfigured.

Andy
--
[-----------[system uptime]--------------------------------------------]
  4:07pm  up 65 days,  7:29,  1 user,  load average: 1.01, 1.02, 1.00