ATTN: Ubuntu 8.04 Users

[dwill]

I've read a few posts now about DNS issues and Ubuntu 8.04 as well as experienced my own problems:

[SOLVED] 32bit to 64bit migration

For me the problem appears as a strange "localhost" resolution error
After three nights of trial and error I believe the problem to be the Multicast DNS discovery service.
Specifically, the order of precedence in the /etc/nsswitch.conf if MDNS is enabled
in Ubuntu 6.06 the hosts line is:

hosts:          files dns mdns

in Ubuntu 8.04 the hosts line is:

hosts:          files mdns4_minimal [NOTFOUND=return] dns mdns4

What I have read point to changing the hosts line to match that of Ubuntu 6.06


does anyone have the ability to test my theory before I spend another 6 hours trying my migration to 8.04 again this evening

[phoenix]

It would appear from reading a few search links that what you've found is causing the problem. The simplest fix would be to revert the nsswitch.conf file to the same entries as 6.06, I don't know when that change was made but it does seem to be causing a lot of problems.

[Klug]

Here's a JeOS (based on 8.04 LTS) nsswitch.conf file (server is used for Zimbra OSE in a VM):

# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.

passwd:         compat
group:          compat
shadow:         compat

hosts:          files dns
networks:       files

protocols:      db files
services:       db files
ethers:         db files
rpc:            db files

netgroup:       nis

And here's an Ubuntu 8.04 LTS 64 bits one (server is the VM host):

# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.

passwd:         compat
group:          compat
shadow:         compat

hosts:          files dns
networks:       files

protocols:      db files
services:       db files
ethers:         db files
rpc:            db files

netgroup:       nis

Both servers were setup in the minimal way (no graphical interface, no LAMP, etc).

The difference with your server seems to be, as you suggested, mDNS/ZeroConf/Bonjour (that is not enabled on my servers as it's not needed).

[phoenix]

Yes, that is what's causing the problem. Changing the nsswitch.conf back to the non-mDNS/ZeroConf/Bonjour settings fixes the problem as per this thread.

Could somebody file a bug report on this problem, please.

[dwill]

There is a bug report filed against Ubuntu. I think it should just be 'noted' for Ubuntu 8.04 server users. It's not Zimbra's problem, though ti does cause problems for Zimbra

I'm testing my migration right now - after the above changes.

[dwmtractor]

For those who either (a) need an overview of installation on 8.04 or (b) would like to help refine the instructions (which I have NOT validated on 64-bit), have a look at this new wiki on installation in Ubuntu 8.04:

Ubuntu 8.04 LTS Server (Hardy Heron) Install Guide - Zimbra :: Wiki

[kevindods]

We had some problems with SSL on the web client. Certificate (commercial) worked fine on the admin console but not in the web client login screen. Got standard Firefox errors about unable to connect. Seems also that with 5.0.11 on Hardy the log file locations are different to the old days, so could not find the Tomcat logs!

Anyhow seems that the standard install didnt configure to allow SSL but thanks to your Hardy wiki entry, minds were cast back to requiring the
zmtlsctl https
or
zmtlsctl mixed
and that seemed to work fine. Just seemed odd mixed wasnt at least configured as a default during the install.

Kevin

[dwmtractor]

Originally Posted by kevindods

Seems also that with 5.0.11 on Hardy the log file locations are different to the old days, so could not find the Tomcat logs!

That's because Zimbra uses Jetty instead of Tomcat now.

Originally Posted by kevindods

Just seemed odd mixed wasnt at least configured as a default during the install.

I agree that's odd. You could file an enhancement bug to ask that mixed be the default config if you care enough. It's no dealbreaker for me because I remember it has to be done and I just do it, but it certainly seems to me to be a reasonable suggestion.

[kevindods]

Jetty - strange how I knew that and didn't connect it before posting - too much mulled wine too early!

SSL - Mixed mode I think could be a fair default. It may be shown somewhere there is noted a reason why it isn't already so but it's worth suggesting.

Thanks!

[ScottChapman]

I am following the instructions in the Wiki.

I modified the named.conf.options file and the resolve.conf

restarted bind9

But I cannot resolve names. ping google.com doesn't resolve.

I know I put my router in as the forwarder (which is what all my machines on my home network use), and put the private IP address of my box in as the nameserver (the private IP is the IP my machine is known as on my local network).

Any ideas?