Page 1 of 3 123 LastLast
Results 1 to 10 of 22

Thread: Install Help Suse 10.1

  1. #1
    rusty741 is offline Member
    Join Date
    Sep 2006
    Posts
    13
    Rep Power
    8

    Default Install Help Suse 10.1

    Hello everyone. I'm getting a few common errors. I'll start with my first problem. I"m also running Suse Linux 10.1.

    My first problem is in the quick install guide it says something like the below:

    ----------------Excerpt from install guide---------------------------
    Important: Make sure that FQDN entry in /etc/hosts appears before the
    hostnames. If this is missing, the creation of the Zimbra certificate fails. The
    FQDN entry should look like this example. See zmcreatecert in the
    Administratorís Guide, CLI Commands appendix.

    127.0.0.1 localhost.localdomain localhost
    your.ip.address FQDN yourhostname
    ------------------end of Excerpt from install guide-------------------

    Here is what my hostfile says file says:

    ---------------------Start my file----------------------------------------
    #
    # hosts This file describes a number of hostname-to-address
    # mappings for the TCP/IP subsystem. It is mostly
    # used at boot time, when no name servers are running.
    # On small systems, this file can be used instead of a
    # "named" name server.
    # Syntax:
    #
    # IP-Address Full-Qualified-Hostname Short-Hostname
    #

    127.0.0.1 localhost

    # special IPv6 addresses
    ::1 localhost ipv6-localhost ipv6-loopback

    fe00::0 ipv6-localnet

    ff00::0 ipv6-mcastprefix
    ff02::1 ipv6-allnodes
    ff02::2 ipv6-allrouters
    ff02::3 ipv6-allhosts
    127.0.0.2 mailhost-rustyriley-com.mailhost.rustyriley.com mailhost-rustyriley-com
    192.168.1.117 mailhost-rustyriley-com.mailhost.rustyriley.com mailhost-rustyriley-com
    ------------------------END OF MY FILE------------------------------------------


    Needless to say it is not looking the way I want it to look and I'm a little confused on how it should look.

    my domain name is rustyriley.com
    Last edited by rusty741; 09-28-2006 at 02:40 PM. Reason: Going to break it up simpler.

  2. #2
    rusty741 is offline Member
    Join Date
    Sep 2006
    Posts
    13
    Rep Power
    8

    Default

    This is for a school project and I have to have the server up and running by next tuesday. I was hoping someone could help me figure out my format for the file above, cause I want to make sure I'm compliant the whole way though the installiation.


    Thanks,
    Rusty Riley

  3. #3
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,491
    Rep Power
    56

    Default

    For some reason your hosts file entry
    Code:
    192.168.1.117 mailhost-rustyriley-com.mailhost.rustyriley.com mailhost-rustyriley-com
    seem to think that your domain name is 'mailhost-rustyriley-com'. You must have given that machine that domain name when you set-up your network connection. I suggest you go itno YaST/Network Devices/Network Card and edit your NIC settings. On the Network Address Setup you need to make sure this PC has a fixed IP and then on Hostname/Server box change the settings. You need your correct domain name and I'd suggest a shorter host name - click OK and come out of YaST and the settings should be saved. That should do what you need.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  4. #4
    rusty741 is offline Member
    Join Date
    Sep 2006
    Posts
    13
    Rep Power
    8

    Default

    Quote Originally Posted by phoenix
    For some reason your hosts file entry
    Code:
    192.168.1.117 mailhost-rustyriley-com.mailhost.rustyriley.com mailhost-rustyriley-com
    seem to think that your domain name is 'mailhost-rustyriley-com'. You must have given that machine that domain name when you set-up your network connection. I suggest you go itno YaST/Network Devices/Network Card and edit your NIC settings. On the Network Address Setup you need to make sure this PC has a fixed IP and then on Hostname/Server box change the settings. You need your correct domain name and I'd suggest a shorter host name - click OK and come out of YaST and the settings should be saved. That should do what you need.

    Thanks man. I think I got it figured out on that part. Here is a dump of my hosts file. It looks close to right.
    -------------------------------------------------------START HOST FILE------------------------------------
    #
    # hosts This file describes a number of hostname-to-address
    # mappings for the TCP/IP subsystem. It is mostly
    # used at boot time, when no name servers are running.
    # On small systems, this file can be used instead of a
    # "named" name server.
    # Syntax:
    #
    # IP-Address Full-Qualified-Hostname Short-Hostname
    #

    127.0.0.1 localhost

    # special IPv6 addresses
    ::1 localhost ipv6-localhost ipv6-loopback

    fe00::0 ipv6-localnet

    ff00::0 ipv6-mcastprefix
    ff02::1 ipv6-allnodes
    ff02::2 ipv6-allrouters
    ff02::3 ipv6-allhosts
    127.0.0.2 mail.rustyriley.com mail
    192.168.1.117 mail.rustyriley.com mail
    -----------------------------END HOST FILE--------------------------------------------------

  5. #5
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,491
    Rep Power
    56

    Default

    Yes, that's almost right. I missed this earlier, you need to change the 127.0.0.1 to this:
    Code:
    127.0.0.1 localhost.localdomain localhost
    and you should be good to go.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  6. #6
    rusty741 is offline Member
    Join Date
    Sep 2006
    Posts
    13
    Rep Power
    8

    Default

    Quote Originally Posted by phoenix
    Yes, that's almost right. I missed this earlier, you need to change the 127.0.0.1 to this:
    Code:
    127.0.0.1 localhost.localdomain localhost
    and you should be good to go.

    Hi Thank you for your help. Here is the error message I'm getting. I'm pretty sure I've set up the MX Server right. Here is what is listed in my domain management settings with MYDOMAIN.com

    MX: mail.rustyriley.com
    A Record: 66.69.168.231

    This is the expert from zimbra install. You can tell it is gettting the IP Address from somewhere.

    zimbra-spell......zimbra-spell-4.0.2_GA_362.SuSE10-20060922134048.i386.rpm...done
    Operations logged to /tmp/zmsetup.log.4765
    Setting defaults... MX: mail.rustyriley.com (66.69.168.231)

    Interface: 192.168.1.117
    Interface: 127.0.0.1
    66.69.168.231
    66.69.168.231


    DNS ERROR - none of the MX records for mail.rustyriley.com
    resolve to this host
    Change domain name? [Yes] yes
    Create Domain: [mail.rustyriley.com] mail.rustyriley.com
    MX: mail.rustyriley.com (66.69.168.231)

    Interface: 192.168.1.117
    Interface: 127.0.0.1


    DNS ERROR - none of the MX records for mail.rustyriley.com
    resolve to this host
    It is suggested that the MX record resolve to this host
    Re-Enter domain name? [Yes] Y
    Create Domain: [mail.rustyriley.com] mail.rustyriley.com
    MX: mail.rustyriley.com (66.69.168.231)

    Interface: 192.168.1.117
    Interface: 127.0.0.1



    DNS ERROR - none of the MX records for mail.rustyriley.com
    resolve to this host
    It is suggested that the MX record resolve to this host
    Re-Enter domain name? [Yes] Create Domain: [mail.rustyriley.com] y


    DNS ERROR resolving MX for y
    It is suggested that the domain name have an MX record configured in DNS
    Re-Enter domain name? [Yes] y
    Create Domain: [mail.rustyriley.com] mail.rustyriley.com
    MX: mail.rustyriley.com (66.69.168.231)

    Interface: 192.168.1.117
    Interface: 127.0.0.1


    DNS ERROR - none of the MX records for mail.rustyriley.com
    resolve to this host
    It is suggested that the MX record resolve to this host
    Re-Enter domain name? [Yes] y
    Create Domain: [mail.rustyriley.com] rustyriley.com
    MX: m1.dnsix.com (63.251.171.163)
    MX: m1.dnsix.com (63.251.171.165)
    MX: m1.dnsix.com (63.251.171.166)
    MX: m1.dnsix.com (63.251.83.84)

    Interface: 192.168.1.117
    Interface: 127.0.0.1


    DNS ERROR - none of the MX records for rustyriley.com
    resolve to this host
    It is suggested that the MX record resolve to this host
    Re-Enter domain name? [Yes] y
    Create Domain: [mail.rustyriley.com] .rustyriley.com
    MX: m1.dnsix.com (63.251.171.165)
    MX: m1.dnsix.com (63.251.171.166)
    MX: m1.dnsix.com (63.251.83.84)
    MX: m1.dnsix.com (63.251.171.163)

    Interface: 192.168.1.117
    Interface: 127.0.0.1


    DNS ERROR - none of the MX records for .rustyriley.com
    resolve to this host
    It is suggested that the MX record resolve to this host
    Re-Enter domain name? [Yes] y
    Create Domain: [mail.rustyriley.com] mail.rustyriley.com
    MX: mail.rustyriley.com (66.69.168.231)

    Interface: 192.168.1.117
    Interface: 127.0.0.1


    DNS ERROR - none of the MX records for mail.rustyriley.com
    resolve to this host
    It is suggested that the MX record resolve to this host
    Re-Enter domain name? [Yes] N

    Here is my etc/HOSTS File as it stands.

    #
    # hosts This file describes a number of hostname-to-address
    # mappings for the TCP/IP subsystem. It is mostly
    # used at boot time, when no name servers are running.
    # On small systems, this file can be used instead of a
    # "named" name server.
    # Syntax:
    #
    # IP-Address Full-Qualified-Hostname Short-Hostname
    #

    127.0.0.1 localhost.localdomain localhost

    # special IPv6 addresses
    ::1 localhost ipv6-localhost ipv6-loopback

    fe00::0 ipv6-localnet

    ff00::0 ipv6-mcastprefix
    ff02::1 ipv6-allnodes
    ff02::2 ipv6-allrouters
    ff02::3 ipv6-allhosts
    127.0.0.2 mail.rustyriley.com mail
    192.168.1.117 mail.rustyriley.com mail
    I've read DNS In a nutshell and been all through the fourmns here and I feel like i'm getting closer to this issue.

    Any help would be greatly apperciated.

    Rusty Riley

  7. #7
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,491
    Rep Power
    56

    Default

    You don't have an A or MX record pointing to your public IP address, that's the problem. You need to make changes to the records so that Zimbra can resolve your mail.rustyriley.com to your public IP.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  8. #8
    rusty741 is offline Member
    Join Date
    Sep 2006
    Posts
    13
    Rep Power
    8

    Default

    Quote Originally Posted by phoenix
    You don't have an A or MX record pointing to your public IP address, that's the problem. You need to make changes to the records so that Zimbra can resolve your mail.rustyriley.com to your public IP.

    I thought my PUBLIC IP is 66.69.168.231. Thats the IP address going to my router. Then on my router I have all of the ports forwarded to 192.168.1.117

  9. #9
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,491
    Rep Power
    56

    Default

    My confusion stems from the fact you said this earlier:
    my domain name is rustyriley.com
    If you check that domain name (which I did earlier) then there is no A or MX records that point to your public IP. After your last post I did a check for a domain name called mail.rustyriley.com and voila, it has an MX record pointing to your IP..... but 'mail.rustyriley.com' is not correct.

    What you need to have is an MX record under your domain records for 'rustyriley.com' that points to your public IP. The name 'mail.rustyriley.com' is the FQDN (Fully Qualified Domain Name) of the computer that runs zimbra, it consists of the name of the machine (mail) and your domain name (rustyriley.com). Look at these tests for mail.rustyriley.com and rustyriley.com they show different results. You also have another problem, if I telnet to port 25 on your public IP then I get a 'connection refused' which means that your server isn't up, your port isn't forwarded to the correct IP or you have a firewall blocking that port.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  10. #10
    rusty741 is offline Member
    Join Date
    Sep 2006
    Posts
    13
    Rep Power
    8

    Default

    Quote Originally Posted by rusty741
    I thought my PUBLIC IP is 66.69.168.231. Thats the IP address going to my router. Then on my router I have all of the ports forwarded to 192.168.1.117

    So I was doing some investigating and I found this posted in the "Pulling my hair out" post

    Hi-
    You don't have an MX record.

    Your MX record needs to point to either:
    1) your router(if you have one), the port forward your router's mta port to your natted IP
    2) your machine.
    My question is, I have my MX pointed to 66.69.168.231

    But then it says the port foward on your router's MTA Port to your natted IP. I guess I'm a little confused there. Below is a list of Ports that I have fowarded to my machine IP address of 192.168.1.117

    7071
    25
    80
    110
    143
    389
    443
    993
    995
    7025

Page 1 of 3 123 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Zimbra fails to install on SuSE 10
    By penpal in forum Installation
    Replies: 10
    Last Post: 12-07-2007, 02:14 PM
  2. Install on (64bit !) SUSE Linux Entreprise Server 10
    By fillide in forum Installation
    Replies: 1
    Last Post: 07-04-2007, 09:06 AM
  3. SUSE 10.1 support
    By michaelkemp2000 in forum Installation
    Replies: 12
    Last Post: 11-02-2006, 08:07 AM
  4. Can't install Beta_M2 on the Suse Linux 10.1
    By sshgz in forum Installation
    Replies: 3
    Last Post: 07-28-2006, 07:30 AM
  5. Install onto Suse 10.1
    By Dirk in forum Installation
    Replies: 9
    Last Post: 05-24-2006, 11:56 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •