Re: How to set auth.allow using hostname?

[Cool <coolbsd@xxxxxxxxxxx>]

Wild guess -

How about DNS revert delegation? Try "host <IP>" to see if it can be mapped back to "hostname1" then there should be something wrong, otherwise you have DNS problem.

-C.B.

P.S. I guessed because I believe whenever a connection comes in, the server does not know anything other than IP and port.

On 12/3/2013 8:38 PM, Mingfan Lu wrote:

In the gluster nodes, I could ping the clients using the hostnames. So, DNS wouldn't be the root cause.

the clients could also resolve the hostnames (ping is ok)

On Wed, Dec 4, 2013 at 11:52 AM, Sharuzzaman Ahmat Raslan <sharuzzaman@xxxxxxxxx> wrote:

How is your DNS setting?

Could your client resolve the hostname?

On Wed, Dec 4, 2013 at 11:49 AM, Mingfan Lu <mingfan.lu@xxxxxxxxx> wrote:

I tried to set auth.allow using hostnames (not IPs) of clients
such as

gluster volume set VOLUME auth.allow hostname1,hostname2,hostname3

But the clients could not mount the volume

If I use IPs, it defintely works.

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.

Any comments?

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users

--
Sharuzzaman Ahmat Raslan

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users

---

This email is free from viruses and malware because avast! Antivirus protection is active.

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users