Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2552

September 19th, 2011 04:00

No reverse lookup for Celerra CIFS server

Hi there,

We have several Celerra boxes with CIFS configured in an AD domain. Our CIFS servers are registered in DNS but they can only be found in forward lookups and not in reverse lookups.

Is this normal behaviour or do we have to add a PTR record by hand?

275 Posts

September 19th, 2011 04:00

By default the Data Mover will not update the PTR record (it is usally not necessary to do so)

There is a param in order to enable PTR updates:

name                = updatePTRrecord
facility_name       = dns
default_value       = 0
current_value       = 0
configured_value    =
user_action         = none
change_effective    = immediate
range               = (0,1)
description         = Allow dynamic PTR updates for DNS

detailed_description

Allows users to enable dynamic updates to PTR records on the DNS server in networks that use static entries for reverse lookup zones in DNS. By default, PTR records are not dynamically updated on the DNS server. param dns updatePTRrecord=0, no updates (default) param dns updatePTRrecord=1, the DM updates the DNS reverse zones for the DM interfaces.

Claude

September 19th, 2011 05:00

Configuring NFS on EMC Celerra.

Never looked at this doc since we have don't use NFS.

September 19th, 2011 05:00

Thank you Claude, that was fast!

Were is this information stored?

Peter

4 Operator

 • 

8.6K Posts

September 19th, 2011 06:00

I believe the reason this is off by default is that some DNS servers wouldn’t allow us to update the pointer records and cause unnecessary error messages.

Rainer

4 Operator

 • 

8.6K Posts

September 19th, 2011 06:00

It should also be listed in the Parameters Guide

23 Posts

November 15th, 2012 10:00

Does this modify change require a reboot? Or should we interpret immediate as no need for reboot? also, is this impacting to existing environment?

Thanks,

Pete

November 16th, 2012 05:00

Changing the parameter does not require a reboot, it only requires restart of the DNS-service.

We use insecure DNS services, we issued the following series of commands to update de box:

Switch on updatePTRrecord
$ server_param server_2 -facility dns -modify updatePTRrecord -value 1
Set dns updates to insecure
$ server_param server_2 -facility dns -modify updateMode -value 1
Restart dns facility
[nasadmin@ZMSSA81401 ~]$ server_dns server_2 -option stop
server_2 : done
[nasadmin@ZMSSA81401 ~]$ server_dns server_2 -option start
server_2 : done

And the PTRrecord is entered into DNS.

Peter

No Events found!

Top