Selfhosted

40347 readers

403 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Should I use a dedicated DHCP/DNS server hardware (lemmy.world)

submitted 10 months ago* (last edited 10 months ago) by Ecclestoned@lemmy.world to c/selfhosted@lemmy.world

30 comments fedilink hide all child comments

My current setup has my DHCP + DNS on my Unifi USG. However, as I have all my apps hosted on a different server (unifi, plex, home assistant, NAS, etc.) I've ran into issues trying to get things set up.

Basically, Unifi needs to know where the unifi server is, but it's assigning the IP address to it.

Should I put DHCP+DNS onto it's own system? Should I put it on my current server? And any non-Pi recommendations for systems? (I've had the PI filesystem clobber itself too many times)

Edit: I'm starting to think that the real problem is having UNIFI on the same system as the server, as it prevents me reconfiguring any of the server routing information without also disconnecting unifi...

Edit 2: I'm going to try switching the server from a static DHCP lease to a static IP. If that's doesn't work, then I think I'll move the unifi server onto it's own system. Thanks!

you are viewing a single comment's thread
view the rest of the comments

[–] empireOfLove2@lemmy.dbzer0.com 11 points 10 months ago (1 children)

Generally speaking, any device ("server") hosting a "service" NEEDS to be assigned a static IP. It simplifies routing significantly and avoids random break problems because DHCP is incredibly stupid at times....

Is there any specific reason you need DHCP to assign an IP to your main hosting server vs setting it all statically?

Moving it to it's own system will not fix the routing problem. You can probably still leave it on the USG.

You should be able to set a fixed static IP on your server, and then also statically assign that same IP to your server in your USG DHCP config- as long as they both are "thinking about" the same IP I think routing should work correctly.

If that breaks, try just assigning the static IP only from the USG side or only from the server's side. I'm 90% sure that even if the USG does not have your server machine in it's client list, if it sends broadcast packets to an entered IP looking for the unifi server, and the unifi server is listening on that manually set IP, they should be able to talk.

disclaimer: i am high as shit right now and this may be bullshit

[–] Ecclestoned@lemmy.world 1 points 10 months ago

Is there any specific reason you need DHCP to assign an IP to your main hosting server vs setting it all statically?

I've done this. I think the real problem is if I ever change the server MAC or IP, as now the unifi server isn't picked up by the USG, which means I can't change the static address.