named.service: Start request repeated too quickly

[Robert Moskowitz]

Wow is it challenging running this down.

I think it may be that I have IPv6 on in BIND and not in the system.

So please wait to comment on my latest fun!

On 7/1/25 4:01 PM, Robert Moskowitz via ubuntu-users wrote:
>
> Tried to get more info, but not informative.
>
> BTW, I am working on porting all my config files from a Centos Named 
> server to Ubuntu, and THINK I have made all the necessary changes. But 
> there is so much in where many of the running files need to go that I 
> have not groked.  as yet.
>
> # journalctl -xeu named.service
>  The job identifier is 6685 and the job result is failed.
> Jul 01 15:41:15 rigel systemd[1]: named.service: Scheduled restart 
> job, restart counter >
>  Subject: Automatic restarting of a unit has been scheduled
>  Defined-By: systemd
>  Support: http://www.ubuntu.com/support
>
>  Automatic restarting of the unit named.service has been scheduled, as 
> the result for
>  the configured Restart= setting for the unit.
> Jul 01 15:41:15 rigel systemd[1]: named.service: Start request 
> repeated too quickly.
> Jul 01 15:41:15 rigel systemd[1]: named.service: Failed with result 
> 'exit-code'.
>  Subject: Unit failed
>  Defined-By: systemd
>  Support: http://www.ubuntu.com/support
>
>  The unit named.service has entered the 'failed' state with result 
> 'exit-code'.
> Jul 01 15:41:15 rigel systemd[1]: Failed to start named.service - BIND 
> Domain Name Serve>
>  Subject: A start job for unit named.service has failed
>  Defined-By: systemd
>  Support: http://www.ubuntu.com/support
>
>  A start job for unit named.service has finished with a failure.
>
>  The job identifier is 6795 and the job result is failed.
>
>
> On 7/1/25 3:46 PM, Robert Moskowitz via ubuntu-users wrote:
>> Oh, man.  NO!
>>
>> I am building a new system that will run BIND9.
>>
>> You may recall I had this error message with UNBOUND a few weeks ago 
>> on a different new system.
>>
>> What is going on here?
>>
>> Is it just DNS servers?  I did not have a problem like this with 
>> other services on similarly build systems.
>>
>> Do I make the same sort of service customizations here?
>>
>> thanks
>>
>>
>>
>
>