I know there are ALOT of posts about this, but...

[Bill Brock]

config will generally have an internal DNS server that is probably not authoritative for your domain and that will contain only the private LAN IP's that Zimbra will use to resolve itself, including the NS records. Then you will of course have your authoritative DNS server that will have your public IP/name resolution. It is confusing to see public IP's in the DNS server Zimbra is using in a split-DNS setup.

[NoDoze]

ns1.domain.com. 116 IN A 71.X.XX.XXX
ns2.domain.com. 116 IN A 71.X.XX.XXX

When I do the dig domain.com any or the dig domain.com mx, these show up. I don't have any public IPs on the zimbra split DNS server. So I would assume it's pulling these from the primary DNS server.

...regardless, this still doesn't solve my problem....

[Bill Brock]

you don't have a DNS server on the local network that Zimbra is using to resolve its local IP. Which is paramount for split DNS. Are you running the Dig commands on the Zimbra server?

[NoDoze]

Yes, running dig on zimbra server, ALL posts I have made are dig from the zimbra server.

primary DNS server = "DNS server on the local network that Zimbra is using to resolve its local IP" ...or so I thought...So then what would I need to do...?

The production zimbra server I have up and running 100% ok, has the exact same setup... why would the test zimbra server need a different setup...?

[NoDoze]

If no one can help me on this...I'm temped to just go ahead and upgrade the production server without testing...

[Bill Brock]

did you tell it to change the domain from mail.domain.com to domain.com?

[NoDoze]

huh?
Tell "it"? What's "it"? The primary DNS server?
I have a live production zimbra server with mail.domain.com
The test server will also be mail.domain.com
Both zimbra servers, the production server AND the test server, are split DNS servers.
Both zimbra servers, have identical setups...
Primary DNS server = 192.168.1.190
Zimbra production server = 192.168.1.248
Zimbra test server = 192.168.1.176

This originally work the first time around, based on this:
Upgrade & Samba problem

However, I have since resolved those issues, and prior to upgrading to 6.0.2 from 5.0.16...I wanted to test the upgrade process with the posix extentions...

I deleted the original install so that I can start fresh (./install -u), and upon reinstalling 5.0.16 onto the test server, now I'm hit with:

zmcontrol start
Host mail.balancehydro.com
Starting ldap...Done.
Unable to determine enabled services from ldap.
Unable to determine enabled services. Cache is out of date or doesn't exist.

previous forum threads suggest a DNS issue... however, since the original setup I haven't even touch any of the DNS settings...I've only done a ./install -u

....SO!?! Can anyone help...?

Thanks!

[NoDoze]

When I do a clean install of 5.0.16, I get NO DNS issues or errors, everything installs correctly, and I'm able to login with the admin.

However, as soon as I change over to the restored version... I get the DNS issues starting it up...

...is there ANY DNS info saved in zimbra's config files? ...that could make this an issue?

Thanks.

[Bill Brock]

Zimbra will try to use the FQDN of the server as the domain instead of just the domain name. This is why I ask. I have always had to change the domain on a clean zimbra install.

Example. If the FQDN of the server is mail.domain.com Zimbra tries to use that as the domain instead of domain.com. In your first dig response that shows your private IP information it appears your domain is mail.domain.com and not domain.com

This is why I ask.

[NoDoze]

Hmmm...shouldn't the resolv.conf with:

nameserver 192.168.1.176
search domain.com

solve that problem though?

So are u saying that I have to change the server hostname to the domain.com, install zimbra, start zimbra, then change it back to mail.domain.com?