Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #11 (permalink)  
Old 10-12-2007, 08:30 AM
Moderator
 
Posts: 1,027
Default

I went around with an installation in this regard too. Problem is a number of people (I see I'm not alone) use the hosts file for some local routing to computers that may not have fully-qualified names (for example, I use one for the backup ftp server in my LAN). ANY non-FQDN will torpedo your installation.

If I were king of the forest, I would like the installer to investigate the hosts entries for localhost and the mailserver itself, and ignore the others. Why should ZCS care if other irrelevant hosts are properly qualified?

Failing that, if before you run your install, you temporarily comment out all your internal hosts addresses, you'll get a clean install. Just don't forget to remove the comment character after you finish so that the other things (like my backup) will continue to run!

Dan
Reply With Quote
  #12 (permalink)  
Old 12-04-2007, 05:57 AM
H A H A is offline
Junior Member
 
Posts: 5
Default

Stupid error got it on CentOS too.
Commented out my local host that don't have a FQDN and it worked.

127.0.0.1 localhost.localdomain localhost
192.168.1.5 server.my.home server

#168.x.x.x server2
#168.x.x.x server3
Reply With Quote
  #13 (permalink)  
Old 06-15-2010, 04:41 AM
Starter Member
 
Posts: 2
Default

A fully qualified domain name (FQDN), sometimes referred to as an absolute domain name,[1] is a domain name that specifies its exact location in the tree hierarchy of the Domain Name System (DNS). It specifies all domain levels, including the top-level domain, relative to the root domain. A fully qualified domain name is distinguished by this absoluteness in the name space.
For example, given a device with a local hostname myhost and a parent domain name example.com, the fully qualified domain name is written as myhost.example.com. This fully qualified domain name therefore uniquely identifies the host — while there may be many resources in the world called myhost, there is only one myhost.example.com.
In the Domain Name System, and most notably, in DNS zone files, a fully qualified domain name is specified with a trailing dot. For example,
somehost.example.com.
specifies an absolute domain name which ends with an empty top level domain label.
The DNS root domain is unnamed, which is expressed by an empty label, resulting in a domain name ending with the dot separator. However, many DNS resolvers will process a domain name that contains a dot in any position as being fully qualified[2] or add the final dot needed for the root of the DNS tree. Resolvers will process a domain name without a dot as unqualified and automatically append the system's default domain name and the final dot.
Some applications, such as web browsers will try to resolve the domain name part of a Uniform Resource Locator (URL) if the resolver cannot find the specified domain or if it is clearly not fully qualified by appending frequently used top-level domains and testing the result. Some applications, however, never use trailing dots to indicate absoluteness, because the underlying protocols require the use of FQDNs, such as Simple Mail Transfer Protocol (e-mail).
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.