Zimbra

NoDoze · #1 (**permalink**) 10-05-2009, 12:44 PM

sigh...ok I'll try to explain this as clear as I can....

I have a primary DNS server at 192.168.1.190

I have a active production zimbra server at 192.168.1.248 with a split DNS setup.

zimbra resolve.conf
DNS1=192.168.1.248
DNS2=192.168.1.190

When I do a nslookup on the zimbra server it resolves showing the 192.168.1.248 ip which is what it's supposed to do....mail.domain.com@192.168.1.248

nslookup mail.domain.com
Server: 192.168.1.248
Address: 192.168.1.248#53

Name: mail.domain.com
Address: 192.168.1.248

Now I just setup a test zimbra server at 192.168.1.176, it too has a split DNS setup...

test resolve.conf
DNS1=192.168.1.176
DNS2=192.168.1.190

But when I do an nslookup on the test server it resolves showing the primary DNS server LAN ip AND the mail.domain.com@71.x.x.x the outside ip address...!?!

nslookup mail.domain.com
Server: 192.168.1.190
Address: 192.168.1.190#53

Name: mail.domain.com
Address: 71.x.xx.xxx

What am I missing here? Cause the split DNS setup is identical...besides the LAN ips of 176 and 248... I don't understand why the test server is resolving this way...?

Thanks!

NoDoze · #2 (**permalink**) 10-05-2009, 02:12 PM

ok, I've assigned a public ip to the test server, but still HAVE not assigned the domain.

The domain mail.domain.com is pointed to the public ip of the active zimbra server...

What would happen if I pointed the same mail.domain.com to two different public ips, one public ip of the active zimbra server and the other public ip to the test zimbra server?

I had a split setup on the test server, but for some reason it's broken. And I don't know why or what I'm missing to get it working again...

For what it looks like the setups are identical, the existing split DNS and the test split DNS....

Thanks.

ArcaneMagus · #3 (**permalink**) 10-05-2009, 02:45 PM

Double check your /etc/resolv.conf file on the test server. It is using 192.168.1.190 as it's primary name resolution rather then 192.168.1.176.

NoDoze · #4 (**permalink**) 10-05-2009, 02:47 PM

the test server resolve.conf has:

nameserver 192.167.1.176
domain localdomain
search domain.com

ArcaneMagus · #5 (**permalink**) 10-05-2009, 02:48 PM

Also try using dig rather then nslookup. nslookup uses it's own internal mechanisms to preform it's lookups. dig uses the system methods and thus is a much better tool for testing things like this.

Code: