# Assigning services to a another/redundant host

**URL:** <https://community.icinga.com/t/assigning-services-to-a-another-redundant-host/15313>\
**Category:** Icinga 2\
**Tags:** icinga2\
**Created:** [December 30, 2025, 4:34pm UTC](https://community.icinga.com/t/assigning-services-to-a-another-redundant-host/15313 "2025-12-30T16:34:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![monigacom](https://community.icinga.com/letter_avatar_proxy/v4/letter/m/bb73d2/32.png) [@monigacom](https://community.icinga.com/u/monigacom)\
**Post date:** [December 30, 2025, 4:34pm UTC](https://community.icinga.com/t/assigning-services-to-a-another-redundant-host/15313/1 "2025-12-30T16:34:55Z")

</div>

Hello,

I’m looking for a way to assign services from one host to another host in case the first host is down. I guess this need will involve “apply dependency” but I’m not sure about its implementation in this case considering the “apply service” will have to be adhered to it.

Please advise, Thank you.

---

<div class="post-metadata">

**Author:** ![Pooh](https://community.icinga.com/letter_avatar_proxy/v4/letter/p/f05b48/32.png) [@Pooh](https://community.icinga.com/u/Pooh)\
**Post date:** [December 30, 2025, 5:27pm UTC](https://community.icinga.com/t/assigning-services-to-a-another-redundant-host/15313/2 "2025-12-30T17:27:23Z")

</div>

My recommendation in this situation is to treat Icinga in exactly the same way  
as whatever is using the services which move from one host to another - assign  
a virtual host in Icinga, which runs the service, and is associated with the  
(presumably) floating address which the machines wanting to use that service  
will connect to.

So, you end up with 3 machines in Icinga - the two “real” servers, and the  
floating service which might be running on one machine or the other, but is  
always associated with the IP address which I’m assuming you move between the  
machines, and which other systems use to connect to that service, no matter  
where it’s running.

If my assumption that you have a floating IP address which is used to access  
this service is incorrect, please give more details about how other systems  
which need to use this service continue to connect to it when it moves from  
one machine to another.

Antony.

---

<div class="post-metadata">

**Author:** ![bkai](https://community.icinga.com/user_avatar/community.icinga.com/bkai/32/841_2.png) [@bkai](https://community.icinga.com/u/bkai)\
**Post date:** [December 31, 2025, 12:47pm UTC](https://community.icinga.com/t/assigning-services-to-a-another-redundant-host/15313/3 "2025-12-31T12:47:53Z")

</div>

The solution with the virtual host sounds good. I have successfully assigned an all-zeros IP address to this host in the past (about 3 years ago, i.e. on an older version of Director) and it worked.

---

<div class="post-metadata">

**Author:** ![bberg](https://community.icinga.com/letter_avatar_proxy/v4/letter/b/b782af/32.png) [@bberg](https://community.icinga.com/u/bberg)\
**Post date:** [January 4, 2026, 3:53pm UTC](https://community.icinga.com/t/assigning-services-to-a-another-redundant-host/15313/4 "2026-01-04T15:53:07Z")

</div>

As far as i understand you i would bind the services to both Hosts, and then use Redundancy Groups to only send notifications in certain cases.

---

<div class="post-metadata">

**Author:** ![Pooh](https://community.icinga.com/letter_avatar_proxy/v4/letter/p/f05b48/32.png) [@Pooh](https://community.icinga.com/u/Pooh)\
**Post date:** [January 4, 2026, 4:16pm UTC](https://community.icinga.com/t/assigning-services-to-a-another-redundant-host/15313/5 "2026-01-04T16:16:09Z")

</div>

I would bind to both hosts only the services which always run on both hosts  
(so, for example, disk or network checks etc), and then bind the services  
which can move between the machines, to the floating virtual host.

This means that Icinga is connecting to the same floating resource as the  
clients which need to use that resource, and can report on connectivity  
problems, service availability etc. This gives you an accurate idea of  
whether clients wanting to use the floating resources will actually be able to.

Antony.

---

<div class="post-metadata">

**Author:** ![monigacom](https://community.icinga.com/letter_avatar_proxy/v4/letter/m/bb73d2/32.png) [@monigacom](https://community.icinga.com/u/monigacom)\
**Post date:** [January 7, 2026, 3:22am UTC](https://community.icinga.com/t/assigning-services-to-a-another-redundant-host/15313/6 "2026-01-07T03:22:57Z")

</div>

Gentlemen, Thank you!
