News for hackers. Stuff that matters.
Re:Let 'localhost' be localhost by im4w1l on Wednesday September 28, 2016 @03:57AM (#12596096)
Maybe I'm overthinking this, but wouldn't a better solution be to say that server1.localhost doesn't have to be loopback, but that it must be resolved by asking the DNS server at localhost (or alternatively defined in the hosts file).

edit: I don't really have any expertise or experience with this at all, just a thought.

Re:Let 'localhost' be localhost by eksu on Wednesday September 28, 2016 @04:00AM (#12596106)
I think people already hosting their own DNS server at localhost don't need to worry about real domain allocations as they can spoof whatever they want for development.

I think reserving .localhost for loopback would be great for my workflow. Maybe it would check hosts for overrides before going straight to loopback?

Re:Let 'localhost' be localhost by LoSboccacc on Wednesday September 28, 2016 @05:27AM (#12596409)
isn't that the role of .localdomain tho?