Multiple DNS entries for Shared Folder Server

Question

Hello everyone,

I have got a question concerning multiple DNS entries of a Shared Folder Server.

On each VNXe 3150 system is a shared folder server (CIFS only) installed that is joined to a Windows domain. Shared Folder Server SRVA on first VNXe is replicating to Shared Folder Server SRVB on second VNXe. Each Shared Folder Server used two independent Ethernet ports, with different IP addresses (eth2 and eth10). One is used for user access. The other one is in a separate VLAN that is used exclusively for replication. User Access is working, also replication.

Setup:

VNX-A

Shared Folder Server SRVA

Eth 10 ---> IP 10.171.240.81 (client VLAN)

Eth 2 ---> IP 192.168.1.81 (replication VLAN)

VNX-B

Shared Folder Server SRVB

Eth 10 ---> IP 10.171.240.82 (client VLAN)

Eth 2 ---> IP 192.168.1.82 (replication VLAN)

During the join process into Windows domain the VNXe automatically creates DNS entries for the Shared Folder Server. This leads to two DNS entries for the Shared folder server. One for each network interface. When looking at DNS entry time stamps it looks like that the VNXe is updating their DNS entries regularly. So manually deleting the DNS host entry on the DNS server is only a temporary solution. We have to be sure that DNS entries only lead to eth10 (client VLAN). How is it possible to change the behaviour of the VNXe so that only the IP address of eth10 is set on the DNS server?

Thanks.

Robert

Swapnil_Chikhal · Answer

Hi Robert,

Above behavior is working as per design. When you join a CIFS server to domain, VNXe makes sure that it updates all possible information for CIFS server to the DNS.

So if you have multiple IP address referring to same FQDN, VNXe will update with same in DNS.

The only work-around as you mentioned is to manually delete second IP from DNS.

Regards,

Swapnil

DynaDin · Answer

Hi Robert,

As Swapnil suggested that's how is designed and registers all IP address of CIFS server. You cannot bypass that.

However, I can suggest you a solution. Instead of creating replication interface (eth2 - 192.168.xx.xx) as second interface for the same CIFS server, create a separate CIFS server with this VLAN IP address. When creating a replication session, use this 192.168.x.x interface. You can use this interface for all replication sessions on that Storage Processor. Create CIFS server on VNXe-B in similar fashion so that source and destination can communicate.

This way your production CIFS server will register only one IP and users will not be impacted.

VNX

Multiple DNS entries for Shared Folder Server

Was this post helpful?