UNSOLVED
Problem with DNS to resolve non-FQDN hostname
Hi,
we started last week with our new Isilon and found that currently it is not possible to use short host names for accessing the SMB shares because our Windows 2008 R2 DNS server is not able to work with Isilon in a way to resolve the short host name pool1.isilon1 . If we use FQDN pool1.isilon1.subdomain.domain.de for the host everything is working fine.
We tracked that the problem only shows up with Win7/Win8 clients. With WinXP the problem does not exist.
A colleague found the cause in the Isilon answering with IPv6 DNS names but our Windows Server does not speak IPv6.
Therefore we'd like to disable IPv6 on the Isilon. Is that possible?
Regards,
daniel
Do you have Primary DNS Suffix defined on your Win7/Win8 Clients?
In my test environment I can access to Isilon without Domain Name.
Isilon side setting:
DNS Search List: project.test.local
SmartConnect Zone Name of a pool: v7
DNS setting:
v7.project.test.local NS cluster.project.test.local
cluster.project.test.local A
Win8 setting:
Primary DNS suffix : project.test.local
I could access cluster by SMB using \\v7\ifs .
I hope this information will help you.
markfoster1
22 Posts
4211
1
Posted June 3rd, 2013 08:00
I do not know of a way to disable IPv6 on the Isilon, but the issue you describe sounds similar to a recently discovered issue in OneFS 7.0.1.x.
The symptoms are a REFUSED response from the SmartConnect DNS server for AAAA names.
An interim solution is to setup SmartConnect zone alias using the FQDN. Or, replace the short name in
the SmartConnect zone name with the FQDN.
You can also open a support case for more detailed analysis of your specific issue.