Neil McGovern wrote: > I'm forwarding this over to debian-admin, as they're the people who can > fix this :) I had already answered Bjoern: Ah yes, the named on saens went alive again. That was not planned. Disabled again. The problem lies somewhere "between" saens and you. It's fine on saens locally. Regards, Joey -- Ten years and still binary compatible. -- XFree86