Comment 17 for bug 370932

I found this bug because I started to observe similar behaviour (10.04): maradns fails to start after reboot, but works flawlessly if started manually later. However, in my case it logs differently, so maybe my case is different:

Mar 2 03:08:20 linode maradns.etc_maradns_mararc: Using default ICANN root servers
Mar 2 03:08:20 linode maradns.etc_maradns_mararc: Log: Root directory changed
Mar 2 03:08:20 linode maradns.etc_maradns_mararc: Fatal error: Problem binding to port 53.
Mar 2 03:08:20 linode maradns.etc_maradns_mararc:
Mar 2 03:08:20 linode maradns.etc_maradns_mararc: System said: Cannot assign requested address

My system receives address via DHCP, so my bet is that maradns attempts to start too early, when system network configuration is not yet ready. Ubuntu version change can impact this by either network manager (which changes the way network starts noticeably) or upstart (which changes whole boot sequence).

Considering ideas above, maybe the best solution would be to convert maradns startup from /etc/init.d script to upstart job which could both be flagged with "start on net-device-up" or sth similar, and annotated with "respawn" just in case...