On Sat, May 12, 2012 at 11:09:22AM +0200, Baptiste wrote: > > Well, I must say I'm unsure what we'll do upon startup, because if we > > accept to start with buggy host names, a number of admins will get > > trapped with errors in their configs causing servers to remain down > > forever. At least right now they know from the beginning that they > > have to fix their configs. Maybe we'll have to support a per-backend > > option to enable delayed host name resolution, I don't know yet. > > > > Regards, > > Willy > > > > I think that you should allow this kind of behavior for people using > Amazon (or any cloud) or people, like Andreas, who uses DHCP+ > automatic DNS update. > So untill the server has startup, it does not know its own IP address > and of course, the DNS resolver can't point to it.
I understand this problem, but I mean that I don't want to make all other users (say 99.99% of users) suffer from a lack of control of configuration errors just because of a few ugly uses (because having a server dynamically addressed is ugly, no matter whatever good excuse you have for this). So I think it will be an option in the backend so that serious users doesn't suffer from this. Cheers, Willy
