I used the DotNetGundam version of "NetInfo Manager" (I think) to set a network alias for the local DNS... I named my computer "localhost", ".localhost", "localhost." and "1.0.0.127.in-addr.arpa".
Net Info Manager sounds familiar, though,
That way, hopefully someone using one of those dumber Linux boxes will try to ssh into his "localhost", get my computer instead, and go insane thinking someone is messing with his box...
Linux n00b luser wrote:
Why the f*ck is localhost going to 10.136.0.100 instead of 127.0.0.1? And when I try to nslookup resolve for 127.0.0.1 it ends up saying I'm "Zaku"? Someone has been messing with my box!
Though, when I change DNS servers to the one at OtherISP and set my domain there... it seems to be fine?
It's in the DNS, you moron.
Screenshots coming soon!
Microsoft Active Directory and DNS Server, unlike that "BIND" aka "BLIND" crap, will allow you to import zone files for the domain "in-addr.arpa". And it will allow you to register as 1.0.0.127 in that domain. Unlike Windows, Linux cannot be configured to set name resolution priorities on servers, so by default it will look up "1.0.0.127.in-addr.arpa" in the DNS server. Instead ofreplying with the requester's name, Active Directory DNS will reply with the name stored in the zone file, which is my PC. Ah, the wonders of Microsoft software!