[Samba] Help: issues about hostname & nameserver
tubocurarine at 163.com
Wed Apr 27 19:24:46 MDT 2011
Another interest thing: if we use a Linux client to access the shares from server, it connects successfully in all cases.
Don't know why.
At 2011-04-28 09:06:59，tubocurarine <tubocurarine at 163.com> wrote:
Thanks for your reply.
But both the wikipeida (http://en.wikipedia.org/wiki/Hostname) and documents provided by CentOS (http://www.centos.org/docs/5/html/5.2/Deployment_Guide/s2-sysconfig-network.html) point out that they should be Fully Qualified Domain Name (FQDN), such ashostname.expample.com.
And also, that does not make sense for the 2nd case in the previous mail.
What's more, I'm interested in how Samba treat the server's hostname. But I failed to search it through the code.
At 2011-04-27 18:41:22，"L.P.H. van Belle" <belle at bazuin.nl> wrote:
>A dot in hostname is not RFC compliant,
>so change the servers hostname.
>>Van: tubocurarine at 163.com
>>[mailto:samba-bounces at lists.samba.org] Namens tubocurarine
>>Verzonden: 2011-04-27 12:03
>>Aan: samba at lists.samba.org
>>Onderwerp: [Samba] Help: issues about hostname & nameserver
>>I'm using Samba-3.5.8 on Linux (Gentoo, amd64) as a file
>>server, and using some Windows based OSes as clinet. And
>>something strange happened to me.
>>Things went as follows:
>>1. If there was no dot (".") in the hostname of server, then
>>no matter whether the DNS server (in /etc/resolv.conf) was set
>>correctly or not, everything went fine. Client can access
>>shares (provided server) normally.
>>2. If there was dot in hostname of server, and if the DNS
>>Server was set correctly (or just left as blank), server
>>3. If there was dot in hostname of server, and the DNS Server
>>was set incorrectly, all client could not connect to the
>>server, with a message indicated that the address of server
>>could not be accessed.
>>My friend and I payed some time on it. We found that in the
>>last situation, the Samba server may spend a long time to look
>>up the computer name (name of server or client). But before
>>the look up ends, the client would treat this as a timeout.
>>I don't know whether we are right about this. And if we were,
>>why everything goes fine in the 2nd case?
>>Any information will be appreciated.
>>To unsubscribe from this list go to the following URL and read the
More information about the samba