<div dir="ltr"><div>In the gluster nodes, I could ping the clients using the hostnames. So, DNS wouldn't be the root cause.<br></div>the clients could also resolve the hostnames (ping is ok)<br><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Dec 4, 2013 at 11:52 AM, Sharuzzaman Ahmat Raslan <span dir="ltr"><<a href="mailto:sharuzzaman@gmail.com" target="_blank">sharuzzaman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>How is your DNS setting?<br><br></div>Could your client resolve the hostname?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 4, 2013 at 11:49 AM, Mingfan Lu <span dir="ltr"><<a href="mailto:mingfan.lu@gmail.com" target="_blank">mingfan.lu@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>I tried to set auth.allow using hostnames (not IPs) of clients <br>such as <br></div>
gluster volume set VOLUME auth.allow hostname1,hostname2,hostname3<br><br>But the clients could not mount the volume<br>
</div>If I use IPs, it defintely works.<br></div>But for my clients use DHCP, so I don't think using IPs is a good idea for they could be changed but hostnames of them wouldn't. <br><br></div>Any comments?<br><div>
<div><div><br></div></div></div></div>
<br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote>
</div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br>Sharuzzaman Ahmat Raslan
</font></span></div>
</blockquote></div><br></div>