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

help-circle







  • I’m in a similar boat, maybe a few steps further down the line than you but not that far.

    Something that is really fun is getting a dynamic DNS set up with duckdns, and then put a certificate on it from certbot and then give all of your containers and self-hosted servers am SSL certificate and name using nginx reverse proxy.

    If you do that and your Wi-Fi router has a VPN option then you can easily get rid of all of the certificate errors on your locally hosted stuff and navigate directly to them with a name rather than typing in IP addresses.

    For me this was daunting but once I actually got it up and running it all made sense.










  • Proof?

    I read 15 different sites about DNS and not a one of them claimed anything like this. They universally all stated that your network attached devices would use the 1st one unless it didn’t respond and only use the 2nd one if the 1st one did not.

    So once again, I ask “Can you send me some more information on this” and not just claim it without any backup information?

    I apologize if I am coming off rude, just my BS meter is getting close to the red zone and I would really appreciate some reliable evidence.


  • Yeah, looks like you don’t know what you’re talking about.

    The second ipv4 DNS address is for redundancy and every network connected system will use the first one as long as it responds.

    It’s perfectly fine to have a single pihole and use something like quad9 as a failover in the unlikely event that your pihole goes down unexpectedly.