• 9 Posts
  • 69 Comments
Joined 2 years ago
cake
Cake day: July 9th, 2023

help-circle




  • What VPS are you using?

    You should be able to setup a firewall, blocking all access to the SSH port. Then setup a VPN so that only you can access via SSH after making your VPN connection.

    If you connect via a static IP, you can also create an ACL for the VPN connection just in case. You can set an ACL for the SSH port forward rule directly as well, but I don’t like that personally. I prefer keeping things behind the VPN.





  • VoIP systems are getting us closer to your example. Properly provisioned VoIP (on-prem or cloud) can take a SIP user which looks exactly like an email address and direct digital calls to a physical phone. These days it’s likely going to be sent to an office desk phone or a Teams user, but many years from now it will likely be more common to dial out like that from/to any phone device.

    I think your example is a bit more nuanced in that there’s some sort of regional database that I suppose one could register for when they change their address. But I don’t think we’re moving in that direction. Things are moving in a decentralized manner and folks hold onto their digital identities, regardless of their geographical location. So like others comments have said, the phone book system is not evolving any further, because modern communication systems are already the evolved version.




  • Well, dig is available also of course, but nearly all distros still include nslookup despite it getting deprecated. I like the simplicity of its interactive mode.

    Host is also really great with more human-readable output.

    Don’t get me wrong, when things are getting hairy, you’re going to make a lot of use of dig. I just find that most troubleshooting can be taken care of a lot simpler with host or nslookup.



  • 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?





  • My dude, I think they blocked you broski… /s

    Just kidding…maybe you have the group silenced?

    • are you just not getting notifications but they still end up in the thread when you open it, or you can’t see them at all?
    • is this happening with all participants in the group?
    • are you on an iPhone or android and which app?
    • if you don’t have anything important in the conversation, maybe try deleting the thread and see if you start receiving from the others
    • Try starting a new group chat from your device.