Installation fails during install of Zimbra-mta RPM

[ddenton]

About the editing. Noticed something I entered incorrectly. Brain no worky. Corrected it. Here's the output from the dig commands.

[root@TB003 zimbra]# dig mydomain.local mx

; <<>> DiG 9.2.4 <<>> mydomain.local mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25161
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mydomain.local.                        IN      MX

;; AUTHORITY SECTION:
.                       900     IN      SOA     A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2007111400 1800 900 604800 86400

;; Query time: 46 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Nov 14 15:00:13 2007
;; MSG SIZE  rcvd: 107

[root@TB003 zimbra]# dig mydomain.local any

; <<>> DiG 9.2.4 <<>> mydomain.local any
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9393
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mydomain.local.                        IN      ANY

;; AUTHORITY SECTION:
.                       873     IN      SOA     A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2007111400 1800 900 604800 86400

;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Nov 14 15:00:40 2007
;; MSG SIZE  rcvd: 107

If there's something in the output that signifies an error, please point it out. "ANSWER: 0" bad?

Thanks a bunch...

[phoenix]

That still shows nothing for your A & MX records. What's in your /etc/resolv.conf file?

[ddenton]

nameserver 127.0.0.1

Thanks for the help...

[ddenton]

Well, it took me doing a dig against our live email domain to see something like I should be seeing. Duh.

[phoenix]

I'm not sure BIND actually listens to 127.0.0.1 in RHEL (or any other distro), you can see from the output in the dig command that it's using an external server for the response. Anyway, change your resolv.conf to the following:

search mydomain.local
nameserver 192.168.100.241

Restart bind and see with the dig commands if you get the correct response. If that works then try the install again.

BTW, you may need to restart your network for it to pick-up the nameserver change - ifdown ethx & ifup ethx.

[ddenton]

Hmm. Changed resolv.conf, rebooted. No dice.

Here's the dig output. Not much different, other than the IP of the server at bottom. Install still also fails.

[root@TB003 zcs]# dig mydomain.local mx

; <<>> DiG 9.2.4 <<>> mydomain.local mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28246
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mydomain.local.                        IN      MX

;; AUTHORITY SECTION:
.                       545     IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2007111400 1800 900 604800 86400

;; Query time: 4 msec
;; SERVER: 192.168.100.241#53(192.168.100.241)
;; WHEN: Wed Nov 14 15:27:36 2007
;; MSG SIZE  rcvd: 107

[root@TB003 zcs]# dig mydomain.local any

; <<>> DiG 9.2.4 <<>> mydomain.local any
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32281
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mydomain.local.                        IN      ANY

;; AUTHORITY SECTION:
.                       410     IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2007111400 1800 900 604800 86400

;; Query time: 4 msec
;; SERVER: 192.168.100.241#53(192.168.100.241)
;; WHEN: Wed Nov 14 15:29:51 2007
;; MSG SIZE  rcvd: 107

[phoenix]

Perhaps I was making a rather hasty assumption about the IP of your BIND server. Is it on the same server as Zimbra and is the IP I told you to paste into resolve.conf the IP of your BIND server?

[soxfan]

In your named.conf file, shouldn't the zone be "mydomain.local", instead of "TB003.mydomain.local"?

Also, not to push off track of getting DNS working properly, because that obviously needs to be working to get Zimbra going, but just another observation. I'm not sure the installation would bomb out like this simply because of DNS not being setup properly. Seems to me like most people with mis-configured DNS run into issues after the install is done. This sounds more like perhaps the installation package is damaged, a disk space issue, or something like that. Maybe I'm wrong and Zimbra has changed things so that people don't get too far if DNS settings are wrong, or maybe this is a NE vs FOSS thing (I've only used FOSS).

[ddenton]

Perhaps I was making a rather hasty assumption about the IP of your BIND server. Is it on the same server as Zimbra and is the IP I told you to paste into resolve.conf the IP of your BIND server?

Yep. They are one in the same. Perhaps it would help to note that this is a test installation. The intention was to get zimbra functional in a fully contained system, in such a way that it could be tested independently of our existing POP3 installation.

The Zimbra/Bind server's internal IP is 192.168.100.241.

[ddenton]

In your named.conf file, shouldn't the zone be "mydomain.local", instead of "TB003.mydomain.local"?

Also, not to push off track of getting DNS working properly, because that obviously needs to be working to get Zimbra going, but just another observation. I'm not sure the installation would bomb out like this simply because of DNS not being setup properly. Seems to me like most people with mis-configured DNS run into issues after the install is done. This sounds more like perhaps the installation package is damaged, a disk space issue, or something like that. Maybe I'm wrong and Zimbra has changed things so that people don't get too far if DNS settings are wrong, or maybe this is a NE vs FOSS thing (I've only used FOSS).

Excellent Soxfan! Making that change in the named conf file produced the following output...

; <<>> DiG 9.2.4 <<>> mydomain.local mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49089
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mydomain.local.                        IN      MX

;; ANSWER SECTION:
mydomain.local.         2592000 IN      MX      10 TB003.mydomain.local.

;; AUTHORITY SECTION:
mydomain.local.         2592000 IN      NS      192.168.100.241.mydomain.local.

;; Query time: 6 msec
;; SERVER: 192.168.100.241#53(192.168.100.241)
;; WHEN: Thu Nov 15 09:49:41 2007
;; MSG SIZE  rcvd: 84

; <<>> DiG 9.2.4 <<>> mydomain.local any
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41620
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;mydomain.local.                        IN      ANY

;; ANSWER SECTION:
mydomain.local.         2592000 IN      SOA     TB003.mydomain.local. hostmaster.TB003.mydomain.local. 10118 43200 3600 3600000 2592000
mydomain.local.         2592000 IN      NS      192.168.100.241.mydomain.local.
mydomain.local.         2592000 IN      A       192.168.100.241
mydomain.local.         2592000 IN      MX      10 TB003.mydomain.local.

;; Query time: 7 msec
;; SERVER: 192.168.100.241#53(192.168.100.241)
;; WHEN: Thu Nov 15 09:51:47 2007
;; MSG SIZE  rcvd: 147

Now for the downer. The install still fails at the same point.