• 0 Posts
  • 67 Comments
Joined 3 years ago
cake
Cake day: July 9th, 2023

help-circle


  • If you want to be able to accept mail, you’ll need to directly expose your mail server on your public IP (router configuration required). You’ll also need to allow your server to egress your WAN as well. That being said - if you really want tighten your security, and don’t care about missing some emails, you could limit your server to seeing only those servers you know you’ll be communicating with, such as work, bank, or GMail servers only.

    You can make it so that retrieving your email with your client of choice requires a VPN connection to your home network also.











  • Yeah if you can dig a record and received a response it’s not a routing issue.

    But aren’t you on the same subnet as your DNS server? There’s no routing happening if you’re on the same subnet which I was assuming.

    Even through dig defaults to outputting A records when no other options are specified, I would use the A option anyway just in case:

    dig @192.168.0.249 study.lan A
    

    If you use “ping study.lan” do you see it output the A record IP address in the first line of output?

    Did you try using nslookup as I described?