Results 1 to 4 of 4

Thread: Almost successful Installation on Ubuntu 8.04 using EC2

  1. #1
    Bugorr is offline New Member
    Join Date
    Dec 2009
    Posts
    3
    Rep Power
    5

    Default Almost successful Installation on Ubuntu 8.04 using EC2

    Hello,

    I've spent two days gathering all latest information about
    installing Zimbra on Ubuntu 32bit using EC2 services.

    Zimbra was installed and I was able to send test email using
    command prompt.

    My problem - I am not able to access domain via browser.

    Ok, Here's my complete configuration.
    (And btw, after I have Zimbra running complete guide will be provided)

    Domain registered with Godaddy.
    NS registered using GD control panel -
    ns1.domain.com

    Server Linux Ubuntu 8.04 Hardy (32 bit)
    Small instance EC2.
    Latest version Zimbra.


    All my configuration files.
    Also I'm attaching print out from dig/nslookup commands.
    Hopefully, someone knowledgeble can take a look and figure out
    why this is happening.

    Thanks a lot in advance.

    Bes regards


    **************named.conf***************
    include "/etc/bind/named.conf.options";

    zone "." {
    type hint;
    file "/etc/bind/db.root";
    };

    zone "localhost" {
    type master;
    file "/etc/bind/db.local";
    };

    zone "127.in-addr.arpa" {
    type master;
    file "/etc/bind/db.127";
    };

    zone "0.in-addr.arpa" {
    type master;
    file "/etc/bind/db.0";
    };

    zone "255.in-addr.arpa" {
    type master;
    file "/etc/bind/db.255";
    };

    include "/etc/bind/named.conf.local";

    **************named.conf.options***************
    options {
    directory "/var/cache/bind";
    //query-source address * port 53;
    forwarders {
    ELASTIC-IP;
    };

    auth-nxdomain no; # conform to RFC1035
    listen-on-v6 { any; };
    };


    **************named.conf.local***************
    zone "domain.com" {
    type master;
    file "/etc/bind/zones/domain.com.db";
    };

    zone "162.210.10.in-addr.arpa" {
    type master;
    file "/etc/bind/zones/rev.E5";
    };

    **************hosts***************
    127.0.0.1 localhost.localdomain localhost
    10.210.162.19 mail.domain.com mail

    # The following lines are desirable for IPv6 capable hosts
    ::1 ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    ff02::3 ip6-allhosts

    **************resolve.conf***************
    search compute-1.internal
    nameserver 10.210.162.19

    **************domain.com.db***************
    $TTL 3600 ; default TTL for zone
    $ORIGIN domain.com.
    @ 3600 IN SOA ns1.domain.com. hostmaster.domain.com. (
    2009101102 ; serial number
    3600 ; refresh
    3600 ; retry
    1209600 ; expire
    3600 ; negative
    )
    @ IN A 10.210.162.19;
    @ IN NS ns1;
    @ IN NS ns2;
    ns1 IN A 10.210.162.19;
    ns2 IN A 10.210.162.19;
    @ IN MX 10 mail;
    www IN A 10.210.162.19;
    mail IN A 10.210.162.19;





    **************domain.com.db***************
    ; <<>> DiG 9.4.2-P2.1 <<>> domain.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58368
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

    ;; QUESTION SECTION:
    ;domain.com. IN A

    ;; ANSWER SECTION:
    domain.com. 3600 IN A 10.210.162.19

    ;; AUTHORITY SECTION:
    domain.com. 3600 IN NS ns1.domain.com.
    domain.com. 3600 IN NS ns2.domain.com.

    ;; ADDITIONAL SECTION:
    ns1.domain.com. 3600 IN A 10.210.162.19
    ns2.domain.com. 3600 IN A 10.210.162.19

    ;; Query time: 0 msec
    ;; SERVER: 10.210.162.19#53(10.210.162.19)
    ;; WHEN: Wed Dec 9 05:10:52 2009
    ;; MSG SIZE rcvd: 117




    **************dig mx***************
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48637
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

    ;; QUESTION SECTION:
    ;domain.com. IN MX

    ;; ANSWER SECTION:
    domain.com. 3600 IN MX 10 mail.domain.com.

    ;; AUTHORITY SECTION:
    domain.com. 3600 IN NS ns2.domain.com.
    domain.com. 3600 IN NS ns1.domain.com.

    ;; ADDITIONAL SECTION:
    mail.domain.com. 3600 IN A 10.210.162.19
    ns1.domain.com. 3600 IN A 10.210.162.19
    ns2.domain.com. 3600 IN A 10.210.162.19

    ;; Query time: 0 msec
    ;; SERVER: 10.210.162.19#53(10.210.162.19)
    ;; WHEN: Wed Dec 9 05:11:21 2009
    ;; MSG SIZE rcvd: 138


    **************nslookup***************
    nslookup domain.com
    Server: 10.210.162.19
    Address: 10.210.162.19#53

    Name: domain.com
    Address: 10.210.162.19

  2. #2
    Bugorr is offline New Member
    Join Date
    Dec 2009
    Posts
    3
    Rep Power
    5

    Default

    Bump, anyone?

    ;!

  3. #3
    Bill Brock is offline Outstanding Member
    Join Date
    May 2007
    Location
    Oklahoma
    Posts
    703
    Rep Power
    8

    Default Does it resolve...

    to a public IP?

  4. #4
    Bugorr is offline New Member
    Join Date
    Dec 2009
    Posts
    3
    Rep Power
    5

    Default

    Well, nslookup returned this
    I can not comment on this, and I am wondering where 172.16.0.23 came from?

    It was in resolv.conf but I've replaced with external IP.

    Hope this helps.

    Bugorr


    nslookup 174.xxx.252.xxx
    Server: 172.16.0.23
    Address: 172.16.0.23#53

    Non-authoritative answer:
    xxx.252.xxx.174.in-addr.arpa name = ec2-174-xxx-252-xxx.compute-1.amazonaws.com.

    Authoritative answers can be found from:
    . nameserver = G.ROOT-SERVERS.NET.
    . nameserver = H.ROOT-SERVERS.NET.
    . nameserver = I.ROOT-SERVERS.NET.
    . nameserver = J.ROOT-SERVERS.NET.
    . nameserver = K.ROOT-SERVERS.NET.
    . nameserver = L.ROOT-SERVERS.NET.
    . nameserver = M.ROOT-SERVERS.NET.
    . nameserver = A.ROOT-SERVERS.NET.
    . nameserver = B.ROOT-SERVERS.NET.
    . nameserver = C.ROOT-SERVERS.NET.
    . nameserver = D.ROOT-SERVERS.NET.
    . nameserver = E.ROOT-SERVERS.NET.
    . nameserver = F.ROOT-SERVERS.NET.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. problem installation in ubuntu lts 8.04
    By diegor in forum Installation
    Replies: 1
    Last Post: 11-04-2009, 10:11 AM
  2. Zimbra-store installation failure on Ubuntu 8.04
    By carpediem in forum Installation
    Replies: 8
    Last Post: 07-27-2009, 01:24 PM
  3. Installation on Ubuntu 8.04 - LDAP faliure 28160
    By 3xca1ibur in forum Installation
    Replies: 5
    Last Post: 07-22-2009, 02:42 AM
  4. Installation problems. Ubuntu 8.04 LTS server
    By itlime in forum Installation
    Replies: 3
    Last Post: 03-03-2009, 11:34 AM
  5. Get emails out of zimbra or get it working again?
    By kingfeanor in forum Migration
    Replies: 9
    Last Post: 11-25-2008, 01:02 AM

Posting Permissions

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