Activity log for bug #205236

Date Who What changed Old value New value Message
2008-03-22 19:11:33 Alexpacio bug added bug
2008-04-20 17:45:21 Adam Sommer bug added attachment 'unnamed' (unnamed)
2008-09-01 13:07:55 Thierry Carrez likewise-open: status New Incomplete
2008-09-01 13:07:55 Thierry Carrez likewise-open: statusexplanation Alexpacio: are you using a .local domain ?
2008-09-01 14:59:24 Thierry Carrez likewise-open: status Incomplete Confirmed
2008-09-01 14:59:24 Thierry Carrez likewise-open: importance Undecided Low
2008-09-01 14:59:24 Thierry Carrez likewise-open: statusexplanation Alexpacio: are you using a .local domain ? Thanks for the info. If you experience problems with Likewise-Open even with your workaround, please file a separate bug with more information on that error that you shouldn't skip. I'll rename this bug so that it points to ".local domains" since it is specific to them. I confirm it doesn't work out of the box if the domain you try to join is named "something.local". This is the result of a war between Microsoft and Apple over the .local domain, with Ubuntu siding with Apple: Ubuntu (like Apple) uses Zeroconf for simple service discovery on LAN, and this makes use of the .local domain. On the other hand, Microsoft AD won't work correctly if its domain name is not served by its own DNS. Using .local for a domain name is therefore a recipe for trouble [1]. If for some reason you have to join an AD domain called "something.local", then you want to disable Zeroconf because the two won't work together. You want the .local DNS domain to be served primarily by the Microsoft DNS and not by Zeroconf. So you edit the /etc/nsswitch.conf file accordingly. [1] http://en.wikipedia.org/wiki/.local
2008-09-01 15:00:05 Thierry Carrez title Likewise Open 4.0.5 doesn't work out of the box in Hardy. Joining .local domains doesn't work out of the box in Hardy