[SOLVED] Zimbra and Linux NOOB here! I know. I know SPLIT DNS!

[phoenix]

Well done on getting it working. Yes, you can certainly set-up internal DNS records to point to your Exchange server.

[robcore3]

Hello Bill

Would i then just create another zone like the db.core3access.com? Is this what the change would look like in the named.conf file?

[root@core3access /]# cat /etc/named.conf
// Default named.conf generated by install of bind-9.2.4.2
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
forwarders { 192.168.1.21 ; 192.168.1.22 ; };
};
include "/etc/rndc.key";
// We are the master server for core3access.com
zone "core3access.com" {
type master;
file "db.core3access.com";
// We are the master server for mail.core3inc.com
zone "mail.core3inc.com" {
type master;
file "db.mail.core3inc.com";
};


By the way, found your solution to opening port 587. I was succesful in getting that working as well. I make sure I look for your postings. Your insight has been a great help in getting my Zimbra solution up and running.

[phoenix]

Yes, the zone is OK but you'll also need an A & MX record pointing at the exchange box - don't forget that Zimbra (postfix) uses DNS for mail server lookup.

[robcore3]

ok.. Good info. I have created my db.core3inc.com. Below is what i have placed in the file:

[root@core3access named]# cat db.core3inc.com
;
; Addresses and other host information.
;
@ IN SOA mail.core3inc.com. hostmaster.core3inc.com. (
10118 ; Serial
43200 ; Refresh
3600 ; Retry
3600000 ; Expire
2592000 ) ; Minimum
; Define the nameservers and the mail servers
IN NS 172.16.0.30
IN A 172.16.0.25
IN MX 10 mail.core3inc.com.


NS - 172.16.0.30 is an internal DNS server. Should i change this to the Zimbra server since it is the NS?
A - 172.16.0.25 is the IP of the Exchange Server

[robcore3]

Trying to start NAMED. /etc/init.d/named start

[root@core3access named]# /etc/init.d/named stop
Stopping named: [ OK ]
[root@core3access named]# /etc/init.d/named start
Starting named:
Error in named configuration:
/etc/named.conf:14: unknown option 'zone'
/etc/named.conf:18: '}' expected near end of file
[FAILED]


Reposting the NAMED.CONF:
[root@core3access /]# cat /etc/named.conf
// Default named.conf generated by install of bind-9.2.4.2
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
forwarders { 192.168.1.21 ; 192.168.1.22 ; };
};
include "/etc/rndc.key";
// We are the master server for core3access.com
zone "core3access.com" {
type master;
file "db.core3access.com";
// We are the master server for mail.core3inc.com
zone "mail.core3inc.com" {
type master;
file "db.core3inc.com";
};

[phoenix]

Take that zone out of the config and restart BIND so you have a working syste otherwise mail will get deferred. Let me ask you another question, I notice you have two forwarders in your BIND set-up - don't those DNS server have records for your Exchange server? What errors did you get when you tried to send to your other domain from Zimbra? Does the domain core3inc.com give the correct responses when you do the following (again, on the zimbra server):

dig core3inc.com mx
dig core3inc.com any

[robcore3]

Here is the resonses:

[root@core3access /]# dig core3inc.com mx

; <<>> DiG 9.3.4-P1 <<>> core3inc.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57291
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 14

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

;; ANSWER SECTION:
core3inc.com. 523 IN MX 10 mail.core3inc.com.

;; AUTHORITY SECTION:
. 518183 IN NS M.ROOT-SERVERS.NET.
. 518183 IN NS A.ROOT-SERVERS.NET.
. 518183 IN NS B.ROOT-SERVERS.NET.
. 518183 IN NS C.ROOT-SERVERS.NET.
. 518183 IN NS D.ROOT-SERVERS.NET.
. 518183 IN NS E.ROOT-SERVERS.NET.
. 518183 IN NS F.ROOT-SERVERS.NET.
. 518183 IN NS G.ROOT-SERVERS.NET.
. 518183 IN NS H.ROOT-SERVERS.NET.
. 518183 IN NS I.ROOT-SERVERS.NET.
. 518183 IN NS J.ROOT-SERVERS.NET.
. 518183 IN NS K.ROOT-SERVERS.NET.
. 518183 IN NS L.ROOT-SERVERS.NET.

;; ADDITIONAL SECTION:
mail.core3inc.com. 3523 IN A 208.14.183.135
A.ROOT-SERVERS.NET. 604583 IN A 198.41.0.4
A.ROOT-SERVERS.NET. 604583 IN AAAA 2001:503:ba3e::2:30
B.ROOT-SERVERS.NET. 604583 IN A 192.228.79.201
C.ROOT-SERVERS.NET. 604583 IN A 192.33.4.12
D.ROOT-SERVERS.NET. 604583 IN A 128.8.10.90
E.ROOT-SERVERS.NET. 604583 IN A 192.203.230.10
F.ROOT-SERVERS.NET. 604583 IN A 192.5.5.241
F.ROOT-SERVERS.NET. 604583 IN AAAA 2001:500:2f::f
G.ROOT-SERVERS.NET. 604583 IN A 192.112.36.4
H.ROOT-SERVERS.NET. 604583 IN A 128.63.2.53
I.ROOT-SERVERS.NET. 604583 IN A 192.36.148.17
J.ROOT-SERVERS.NET. 604583 IN A 192.58.128.30
K.ROOT-SERVERS.NET. 604583 IN A 193.0.14.129

;; Query time: 2 msec
;; SERVER: 192.168.1.127#53(192.168.1.127)
;; WHEN: Sat Aug 16 01:06:14 2008
;; MSG SIZE rcvd: 510


[root@core3access /]# dig core3inc.com any

; <<>> DiG 9.3.4-P1 <<>> core3inc.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6319
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 14

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

;; ANSWER SECTION:
core3inc.com. 493 IN MX 10 mail.core3inc.com.

;; AUTHORITY SECTION:
. 518153 IN NS E.ROOT-SERVERS.NET.
. 518153 IN NS F.ROOT-SERVERS.NET.
. 518153 IN NS G.ROOT-SERVERS.NET.
. 518153 IN NS H.ROOT-SERVERS.NET.
. 518153 IN NS I.ROOT-SERVERS.NET.
. 518153 IN NS J.ROOT-SERVERS.NET.
. 518153 IN NS K.ROOT-SERVERS.NET.
. 518153 IN NS L.ROOT-SERVERS.NET.
. 518153 IN NS M.ROOT-SERVERS.NET.
. 518153 IN NS A.ROOT-SERVERS.NET.
. 518153 IN NS B.ROOT-SERVERS.NET.
. 518153 IN NS C.ROOT-SERVERS.NET.
. 518153 IN NS D.ROOT-SERVERS.NET.

;; ADDITIONAL SECTION:
mail.core3inc.com. 3493 IN A 208.14.183.135
A.ROOT-SERVERS.NET. 604553 IN A 198.41.0.4
A.ROOT-SERVERS.NET. 604553 IN AAAA 2001:503:ba3e::2:30
B.ROOT-SERVERS.NET. 604553 IN A 192.228.79.201
C.ROOT-SERVERS.NET. 604553 IN A 192.33.4.12
D.ROOT-SERVERS.NET. 604553 IN A 128.8.10.90
E.ROOT-SERVERS.NET. 604553 IN A 192.203.230.10
F.ROOT-SERVERS.NET. 604553 IN A 192.5.5.241
F.ROOT-SERVERS.NET. 604553 IN AAAA 2001:500:2f::f
G.ROOT-SERVERS.NET. 604553 IN A 192.112.36.4
H.ROOT-SERVERS.NET. 604553 IN A 128.63.2.53
I.ROOT-SERVERS.NET. 604553 IN A 192.36.148.17
J.ROOT-SERVERS.NET. 604553 IN A 192.58.128.30
K.ROOT-SERVERS.NET. 604553 IN A 193.0.14.129

;; Query time: 2 msec
;; SERVER: 192.168.1.127#53(192.168.1.127)
;; WHEN: Sat Aug 16 01:06:44 2008
;; MSG SIZE rcvd: 510

my forwarders are Microsoft DNS servers in the DMZ. Same subnet as the Zimbra server.

Below is an export from the Core3inc.com zone:
Name Type Data
www CNAME core3inc.com.
webmail A 208.14.183.145
pscwebmail A 208.14.183.145
ns2 A 208.14.183.142
ns1 A 208.14.183.141
mail A 208.14.183.135

(same as parent folder) SOA [176], ns2.core3inc.com., admin.core3inc.com.
(same as parent folder) NS ns3-auth.sprintlink.net.
(same as parent folder) NS ns2.core3inc.com.
(same as parent folder) NS ns2-auth.sprintlink.net.
(same as parent folder) NS ns1.core3inc.com.
(same as parent folder) NS ns1-auth.sprintlink.net.
(same as parent folder) MX [10] mail.core3inc.com.
(same as parent folder) A 208.14.183.160
(same as parent folder) A 208.14.183.149

[phoenix]

What errors did you get when you tried to send an email from the Zimbra server to your exchange domain? I seem to be getting some strange responses for your exchange domain, check the report here: Quick Check - Pingability.com

[robcore3]

Hello Bill

I have resolved the problem. Below is my named.conf:

[root@core3access /]# cat /etc/named.conf
// Default named.conf generated by install of bind-9.2.4.2
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
forwarders { 172.16.0.24 ; 192.168.1.21 ; 192.168.1.22 ; };
};
include "/etc/rndc.key";
// We are the master server for core3access.com
zone "core3access.com" {
type master;
file "db.core3access.com";
};
// We are the master server for mail.core3inc.com
zone "mail.core3inc.com" {
type master;
file "db.core3inc.com";
};


Made the adjustment in the db.core3inc.com. I was able to start NAMED. Performed my NSLOOKUP of core3inc.com and it pointed to my internal IP address.

Success of sending email to my internal email server.

Thanks for your help Bill. Great working with you. Now the real work begins. Learning how the administration part.

[phoenix]

Glad you've got it working. Have a good week-end.