• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle

  • I have to admit, I’m a bit confused.

    I have dns records already in my domain provider pointing to a tailscale ip

    I want to know what I have to do to get minecraft.example.com to resolve interenally.

    Since your domain resolves to an internal private Tailscale IP and your question is how to access using the domain, locally…. I feel like there’s an error in your architecture here. Wouldn’t any device that is on your Tailscale private network already have access using the domain name? If by “resolve internally” you mean hosts on your LAN, not connected to Tailscale scale? How would that be possible if it resolves to a Tailscale IP. If you have control of your DNS on your LAN, you could simply add an override and point it to the LAN address of the Minecraft server.









  • It seems that the commenter’s intention was clear to everyone except you. The commenter acknowledged the need for RAID software or a specific file system, mentioning that it had already been addressed. Understood the budget and OP being an newb.

    Although their tone may have been blunt, they stayed focused on their original point.

    But you just kept nagging. lol

    Either way OP was helped and now you can sleep knowing you did your part. A true internet hero.





  • Your network is probably configured with inconsistent subnets / netmasks. iOS / Android are on WiFi and getting a different subnet/netmask than your severs.

    Edit: What does pinging the server with nmap mean? Are you checking open ports or pinging the server? That doesn’t make sense or at least leaves us with more questions with the way you worded that. Although the nmap utility can provide both of those answers, I’m not sure that’s what you meant. Technically nmap and ping are two different tools.


  • prometheus and grafana … seems to be the universally accepted solution for self-hosted monitoring

    Not exactly. There are many ways to do this. Most of us just use this solution because its easily scalable, highly documented and what we are probably already doing currently at work.

    all built into one container

    It’s nice to separate data sources from the dashboards and alerting platforms. It’s scalable and extremely light weight and gives you more options.

    On top of prometheus not seeming useful on its own …

    Yeah, that’s just not always true. Maybe for you, in your use case.

    Installing a Prometheus node exporter gives you an easily accessible end point with JSON data that can be used however you like. Modularity is a good thing. Being able to swap parts in and out with other parts is a good thing.

    If you haven’t figured it out yet, there is not an exact correct answer here, use what fits your needs. While I have a dash board setup in grafana, it’s not my main use case. Since the data is available from all the node-exporters on all my hardware, I wrote up my own alerting scripts and automations using python.

    That’s the beauty of modularity and standards when self hosting.