On 12/04/2013 12:26 PM, Mingfan Lu wrote:
the change for the bug seems more reasonable, that get the ips for hostname in server side then comparet with the incoming client's ip. So, we don't need the DNS reverse lookup for the incoming client's IP. But the fix is well tested and ready to backport? <https://bugzilla.redhat.com/show_bug.cgi?id=915153>
Needs some review attention and testing help. If we can accomplish both, I think we can pull this in for 3.5.
-Vijay
On Wed, Dec 4, 2013 at 2:07 PM, shwetha <spandura@xxxxxxxxxx <mailto:spandura@xxxxxxxxxx>> wrote: Refer to bug : https://bugzilla.redhat.com/show_bug.cgi?id=915153 On 12/04/2013 11:11 AM, Cool wrote:Means you'd better use IP instead of host name, or you have to ask your DNS administrator to setup reverse DNS (PTR record) for those IPs, which may involve your upstream ISP, or even more complicated than that ... http://en.wikipedia.org/wiki/Reverse_DNS_lookup - C.B. On 12/3/2013 9:24 PM, Mingfan Lu wrote:host(a.b.c.d) I got, Host a.b.c.d.in-addr.arpa. not found: 3(NXDOMAIN) a.b.c.d stands for the ip address of my client. On Wed, Dec 4, 2013 at 1:18 PM, Cool <coolbsd@xxxxxxxxxxx <mailto:coolbsd@xxxxxxxxxxx>> wrote: 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 <mailto: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 <mailto: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 <mailto:Gluster-users@xxxxxxxxxxx> http://supercolony.gluster.org/mailman/listinfo/gluster-users -- Sharuzzaman Ahmat Raslan _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx <mailto:Gluster-users@xxxxxxxxxxx> http://supercolony.gluster.org/mailman/listinfo/gluster-users------------------------------------------------------------------------ <http://www.avast.com/> This email is free from viruses and malware because avast! Antivirus <http://www.avast.com/> protection is active.------------------------------------------------------------------------ <http://www.avast.com/> This email is free from viruses and malware because avast! Antivirus <http://www.avast.com/> protection is active. _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx <mailto:Gluster-users@xxxxxxxxxxx> http://supercolony.gluster.org/mailman/listinfo/gluster-users_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
