Hi Chjatwork,

I suppose you want to create a Linux Bind DNS setup for use with smartconnect, not use with smartpools. Because Smartpools software is used for optimizing your scale-out storage resources with automated storage tiering. Is it right?

For example, the two lines of text will look similar to:

sc-nfspool.company.com. IN A 10.7.149.100

nfspool.company.com. IN NS sc-nfspool.company.com.

from:

Isilon OneFS: How to create a UNIX-based BIND DNS setup for use with SmartConnect

Here, sc-nfspool is the name for the fixed IP of the Isilon SmartConnect Adv DNS server lives.

nfspool is the name to be used as server when mounting from the SC zone (for a given address "pool" ;-)

hth

--Peter

Jeffey,

Correct we need SmartConnect to help us to do load balance on this secondary network that Isilon is connected to.  No need for SmartPools because we don't have but the NL-400s all with the same type of spinning disk in them.

I was wondering if someone was able to make this work.  Using BIND version 9 and implementing the said configuration in https://support.emc.com/kb/89758

doesn't work.

Check out the newest guide for step-by-step troubleshooting of SmartConnect issues:

https://www.emc.com/collateral/TechnicalDocument/docu63149.pdf

Configuring BIND for Isilon seems to be very tricky - in our cases the problem was the forwarders weren't enable for that particular zone.

Depending on your BIND configuration, it may be necessary to add line like the following for the particular isilon zone:

forwarders {Service.IP.Of.Isilon;};