I am very thankful for reply, @wfburton, but I am having a hard time understanding it properly. I blame my inexperience with networking …
produces the following, when ran from within the same ((W)LAN) network as the server:
and gives the following:
And finally, from the server itself (= monolith), oddly enough gives me:
From then on, I admit, I am lost as to what you tried to have me do :]
Code:
nslookup monolith.wheremymonkeyis.at 192.168.88.1Code:
Server: 192.168.88.1Address: 192.168.88.1#53Non-authoritative answer:Name: monolith.wheremymonkeyis.atAddress: 192.168.88.112Code:
nslookup -q=SOA monolith.wheremymonkeyis.at 192.168.88.1Code:
Server: 192.168.88.1Address: 192.168.88.1#53Non-authoritative answer:*** Can't find monolith.wheremymonkeyis.at: No answerAuthoritative answers can be found from:Code:
ping monolith.wheremymonkeyis.at Code:
PING monolith.wheremymonkeyis.at(monolith.wheremymonkeyis.at (fe80::9e6b:ff:fe1a:79ae%enp3s0)) 56 data bytes64 bytes from monolith.wheremymonkeyis.at (fe80::9e6b:ff:fe1a:79ae%enp3s0): icmp_seq=1 ttl=64 time=0.055 ms64 bytes from monolith.wheremymonkeyis.at (fe80::9e6b:ff:fe1a:79ae%enp3s0): icmp_seq=2 ttl=64 time=0.037 ms64 bytes from monolith.wheremymonkeyis.at (fe80::9e6b:ff:fe1a:79ae%enp3s0): icmp_seq=3 ttl=64 time=0.028 ms64 bytes from monolith.wheremymonkeyis.at (fe80::9e6b:ff:fe1a:79ae%enp3s0): icmp_seq=4 ttl=64 time=0.031 msStatistics: Posted by hook — Mon Dec 25, 2023 10:37 pm