#nobridge

  • 0 Posts
  • 241 Comments
Joined 10 months ago
cake
Cake day: March 14th, 2025

help-circle


  • When nslookup google.com from a laptop on this LAN, it returns Server: 10.2.0.1 Address: 10.2.0.1#53

    nonauthoritative answer: google.com with ip information repeated.

    I don’t under stand this return as it’s an ip outside my lan net and dhcp provisioning.

    I’m unclear on what you’re confused about regarding the above quote. Here comes an explanation of nslookup.
    The command is nslookup <domain> <dns-server> and if dns-server is empty it uses your default. F.e.:

    ***@fedoragaming:~$ nslookup www.google.com 8.8.8.8

    The response starts by telling you which <dns-server> it used for the lookup and which address including port was used:

    Server: 8.8.8.8
    Address: 8.8.8.8#53

    It then gives you the answer on where to find the <domain>, once for ipv4 and once for ipv6:

    Non-authoritative answer:
    Name: www.google.com
    Address: 142.251.142.228
    Name: www.google.com
    Address: 2a00:1450:400f:807::2004

    edit: I think I understand your question a bit better now. To check which dns-server you’re using do a “cat /etc/resolve.conf”
    If you run a distro with systemd then use the command “resolvectl status”















  • A big point of a NAS in my mind is to run some sort of redundancy, which means you will want to setup a RAID on the drives in the NAS, and that in turn means that my recommendation wouldn’t be to chuck existing drives into the NAS solution but to setup the NAS drives and then copy your data to it.

    Dedicated NAS hardware storage is usually accessed over SMB, NFS or SFTP and most software has support for one of those protocols.
    Some services can have hiccups when running against networked storage, f.e. Jellyfin might lose library metadata if the Jellyfin service’s library scan is started and the networked storage is unavailable.