DNS and zmsetup.pl issue

[agenerette]

I believe I've setup the necessary A and MX records for my domain and I've installed ldap, but zmsetup.pl is failing for me. The errors are related to name resolution and ldap setup. Here's a recent log file from one of my attempts:

Mon Aug 22 21:09:59 2011 Operations logged to /tmp/zmsetup.08222011-210959.log
Mon Aug 22 21:09:59 2011 Installing LDAP configuration database...
Mon Aug 22 21:09:59 2011 done.
Mon Aug 22 21:09:59 2011 *** Running as zimbra user: /opt/zimbra/libexec/zmldapschema 2>/dev/null
Looking for LDAP installation...succeeded
Installing core schema...
Installing cosine schema...
Installing inetOrgPerson schema...
Installing zimbra schema...
Installing amavis schema...
Installing dynlist schema...
Mon Aug 22 21:10:00 2011 Getting installed packages
Mon Aug 22 21:10:00 2011 checking isEnabled zimbra-core
Mon Aug 22 21:10:00 2011 zimbra-core not in enabled cache
Mon Aug 22 21:10:00 2011 enabled packages
Mon Aug 22 21:10:00 2011 Newinstall enabling all installed packages
Mon Aug 22 21:10:00 2011 Enabling zimbra-core
Mon Aug 22 21:10:00 2011 Enabling zimbra-ldap
Mon Aug 22 21:10:00 2011 Enabling zimbra-store
Mon Aug 22 21:10:00 2011 Enabling zimbra-mta
Mon Aug 22 21:10:00 2011 Enabling zimbra-snmp
Mon Aug 22 21:10:01 2011 Enabling zimbra-logger
Mon Aug 22 21:10:01 2011 Enabling zimbra-apache
Mon Aug 22 21:10:01 2011 Enabling zimbra-spell
Mon Aug 22 21:10:01 2011 Enabling zimbra-memcached
Mon Aug 22 21:10:01 2011 Enabling zimbra-proxy

...

Mon Aug 22 21:10:05 2011 No results returned for A lookup of directory-srv.kidquipment.com
Mon Aug 22 21:10:05 2011 Checked nameservers:
Mon Aug 22 21:10:05 2011 127.0.0.1
Mon Aug 22 21:10:05 2011 216.154.208.5
Mon Aug 22 21:10:05 2011

DNS ERROR resolving directory-srv.kidquipment.com
Mon Aug 22 21:10:05 2011 It is suggested that the hostname be resolveable via DNS
Mon Aug 22 21:12:34 2011

DNS ERROR resolving MX for directory-srv.kidquipment.com
Mon Aug 22 21:12:34 2011 It is suggested that the domain name have an MX record configured in DNS
Mon Aug 22 21:12:35 2011 done.
Mon Aug 22 21:12:35 2011 checking isEnabled zimbra-ldap
Mon Aug 22 21:12:35 2011 zimbra-ldap is enabled

...

Mon Aug 22 21:12:40 2011 checking isEnabled zimbra-ldap
Mon Aug 22 21:12:40 2011 zimbra-ldap is enabled
Mon Aug 22 21:12:40 2011 checking isEnabled zimbra-store
Mon Aug 22 21:12:40 2011 zimbra-store is enabled
Mon Aug 22 21:12:40 2011 This is the ldap master and ldap hasn't been configured yet.
Mon Aug 22 21:12:40 2011 This is the ldap master and ldap hasn't been configured yet.
Mon Aug 22 21:12:40 2011 This is the ldap master and ldap hasn't been configured yet.

...

Mon Aug 22 21:12:41 2011 This is the ldap master and ldap hasn't been configured yet.
Mon Aug 22 21:12:41 2011 checking isEnabled zimbra-store
Mon Aug 22 21:12:41 2011 zimbra-store is enabled
Mon Aug 22 21:12:41 2011 This is the ldap master and ldap hasn't been configured yet.
Mon Aug 22 21:12:41 2011 This is the ldap master and ldap hasn't been configured yet.
Mon Aug 22 21:12:41 2011 This is the ldap master and ldap hasn't been configured yet.
Mon Aug 22 21:12:41 2011 checking isEnabled zimbra-proxy
Mon Aug 22 21:12:41 2011 zimbra-proxy is enabled
Mon Aug 22 21:12:41 2011 checking isEnabled zimbra-proxy
Mon Aug 22 21:12:41 2011 zimbra-proxy is enabled
Mon Aug 22 21:12:41 2011 checking isEnabled zimbra-proxy
Mon Aug 22 21:12:41 2011 zimbra-proxy is enabled
Mon Aug 22 21:12:41 2011 This is the ldap master and ldap hasn't been configured yet.
Mon Aug 22 21:12:41 2011 This is the ldap master and ldap hasn't been configured yet.

[phoenix]

Originally Posted by agenerette

I believe I've setup the necessary A and MX records for my domain and I've installed ldap, but zmsetup.pl is failing for me.

Then you need to provide some confirmation that they are correct - post the output of all the commands in the 'Verify...' section of the Split DNS article.

Originally Posted by agenerette

The errors are related to name resolution and ldap setup.

According to the output above, there is no A record.

BTW, you should not enable the imapproxy nor memcached on a single server it will cause you problems.

I'd suggest you fix your DNS (and/or hosts file) problem then remove zimbra with the following command:

./install.sh -u

When you've done that, install zimbra again but make sure the DNS etc. is fixed first.

[agenerette]

Actually, the 1st thing I did, today was run instal.sh -u. I'll re-run it, though, to get rid of imapproxy and memcached. I thought I had the dns stuff setup the way it needed to be. Attached is a screen-shot of the setup with my provider.

Here's the output from dig kidquipment.com mx:

dig kidquipment.com mx

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> kidquipment.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33770
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

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

;; ANSWER SECTION:
kidquipment.com. 2592000 IN MX 10 directory-srv.kidquipment.com.

;; AUTHORITY SECTION:
kidquipment.com. 2592000 IN NS ns.kidquipment.com.

;; ADDITIONAL SECTION:
ns.kidquipment.com. 2592000 IN A 68.169.54.94

;; Query time: 5 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Aug 23 15:36:30 2011
;; MSG SIZE rcvd: 96


and the output from dig kidquipment.com any:

dig kidquipment.com any

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> kidquipment.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53324
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;kidquipment.com. IN ANY

;; ANSWER SECTION:
kidquipment.com. 2592000 IN SOA kidquipment.com. hostmaster.kidquipment.com. 2011030801 43200 3600 3600000 2592000
kidquipment.com. 2592000 IN NS ns.kidquipment.com.
kidquipment.com. 2592000 IN A 68.169.54.94
kidquipment.com. 2592000 IN MX 10 directory-srv.kidquipment.com.

;; ADDITIONAL SECTION:
ns.kidquipment.com. 2592000 IN A 68.169.54.94

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Aug 23 15:39:33 2011
;; MSG SIZE rcvd: 159



Now, unless I'm reading it wrong (certainly possible, no doubt) these lines are saying that I have what I need:

ns.kidquipment.com. 2592000 IN A 68.169.54.94

kidquipment.com. 2592000 IN MX 10 directory-srv.kidquipment.com.

I'm not sure what the problem might be. Yesterday I got this

# host $(hostname)
directory-srv.kidquipment.com has address 68.169.54.94
directory-srv.kidquipment.com mail is handled by 10 mx10.directory-srv.kidquipment.com.

But today, I'm getting

# host $(hostname)
Host directory-srv.kidquipment.com not found: 3(NXDOMAIN)

[agenerette]

Oh, and here's the hosts and resolv.conf info:

# cat /etc/hosts
########## Automatically generated by OnApp (2.1.0)
127.0.0.1 localhost.localdomain localhost
68.169.54.94 directory-srv.kidquipment.com directory-srv
[root@directory-srv /]# cat /etc/resolv.conf
########## Automatically generated by OnApp (2.1.0)
domain kidquipment.com
nameserver 127.0.0.1
#nameserver 216.154.208.4
nameserver 216.154.208.5

[phoenix]

Originally Posted by agenerette

.... I thought I had the dns stuff setup the way it needed to be.

There is no A record in that output for your mail server, you need one.

[agenerette]

My host's name is directory-srv.kidquipment.com

directory-srv.kidquipment.com A 68.169.54.94

kidquipment.com MX directory-srv.kidquipment.com - priority: 10

These entries aren't sufficient? If not, then what am I missing?

[agenerette]

This is maddening. directory-srv.kidquipment.com doesn't resolve, but mail.kidquipment.com does.

nslookup
> directory-srv
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find directory-srv: NXDOMAIN
> mail
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: mail.kidquipment.com
Address: 68.169.54.94
>

But mail just has a cname record that points it to directory-srv.

[phoenix]

Originally Posted by agenerette

This is maddening. directory-srv.kidquipment.com doesn't resolve, but mail.kidquipment.com does.



But mail just has a cname record that points it to directory-srv.

You do not use CNAME records for a mail server, they cause problems - use correct A & MX records.

[agenerette]

Ok, I've deleted the cname record, but what's wrong with my mx and a record entries for directory-srv? Another provider that I've communicated with on this says:

Running an nslookup query on directory-srv.kidquipment.com subdomain I get:

nslookup directory-srv.kidquipment.com
Name: directory-srv.kidquipment.com
Address: 68.169.54.94

The subdomain is properly resolving to 68.169.54.94 IP address.


So, I don't know why I'm still having trouble.

[phoenix]

I've already given you the answer in post #5, there was no A record for your mail server in the output you posted.