Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
PowerScale: Network Design Considerations
Executive summary Network architecture design Latency, bandwidth, and throughput Ethernet flow control SyncIQ considerations Quality of Service (QoS) Software-Defined Networking PowerScale OneFS ports SmartConnect considerations
Introduction
SmartConnect network hierarchy
Load balancing
Static or dynamic IP address allocation
Dynamic failover
Protocols and SmartConnect allocation methods
IP address quantification
SmartConnect service name
SmartConnect node suspension
SmartConnect and Reverse DNS
DNS delegation best practices
SmartConnect DNS, subnet, and pool design
SmartConnect in isolated network environments
DNS and time-to-live
Flushing DNS and OneFS
Where the SmartConnect Service IP runs (pre OneFS 8.2)
SmartConnect Multi-SSIP
Other SmartConnect considerations
Ethernet, MTU, and IP overhead Access Zones best practices Source-Based Routing considerations Isilon 6th generation 1 GbE interfaces Intelligent Platform Management Interface IPv6 OneFS host-based firewall Network troubleshooting Appendix A: Supported network optics and transceivers Appendix B: Technical support and resources

SmartConnect and Reverse DNS

SmartConnect and Reverse DNS

  • Usually, we recommend that PowerScale SmartConnect Service IP addresses and SmartConnect zone names do not have reverse DNS entries, also known as pointer (PTR) records.

    In certain environments where PTR records are required, many PTR entries might be created because PowerScale SmartConnect pools could have hundreds of IP addresses. In scenarios where PTR records are required, each time an additional IP address is added to a SmartConnect pool, DNS changes are necessary to keep the environment consistent.

    Creating reverse DNS entries for the SmartConnect Service IP’s Host [address, or A] record is acceptable if the SmartConnect Service IP is referenced only with an A record in one DNS domain.