# Run pi-hole on an additional ip

**URL:** <https://discourse.pi-hole.net/t/run-pi-hole-on-an-additional-ip/3690>\
**Category:** Feature Requests\
**Created:** [June 16, 2017, 9:45am UTC](https://discourse.pi-hole.net/t/run-pi-hole-on-an-additional-ip/3690 "2017-06-16T09:45:05Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![bcutter](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bcutter/32/5769_2.png) [@bcutter](https://discourse.pi-hole.net/u/bcutter)\
**Post date:** [April 6, 2025, 5:27pm UTC](https://discourse.pi-hole.net/t/run-pi-hole-on-an-additional-ip/3690/12 "2025-04-06T17:27:49Z")

</div>

I need to bring this topic on the table again unfortunately, as the methods outlined here are not working anymore due to e. g. an updated Linux environment (neither `dhcpcd5` nor `/etc/network/interfaces` in use anymore).

### What is the preferred solution to bind Pi-Hole/webinterface (lighttpd on Pi-Hole v5) on a virtual eth0:0 interface and not use the primary eth0 too nowadays?

Details on my specific current situation at

> [@Conflict with other webservices running on Pi (Ports 80 and 443)](https://discourse.pi-hole.net/t/conflict-with-other-webservices-running-on-pi-ports-80-and-443/2329/73):
>
> This seems to not work anymore: I'm currently in the progress of migrating a Pi-Hole v5 instance to another host and keep the v5 version and all settings, history etc. Meanwhile on the new host, as /etc/network/interfaces is not being used anymore (Pi OS 12) I used /etc/systemd/network/eth0.network to set the static primary IP for the host (which should be used by the other service) --\> 192.168.0.55 / eth0 /etc/network/if-up.d/eth0-alias to set the static secondary (virtual) IP which shoul…

Hints warmly welcome.

* * *

### EDIT: Solved, still working the same way.

---

_[View the full topic](https://discourse.pi-hole.net/t/run-pi-hole-on-an-additional-ip/3690)._