I have a development server on my LAN with a static IP address. My DD-WRT flashed router assigns the domain 'server.local' to the static IP of the server. Everything worked fine with my setup. I could connect to the server via ssh, ftp, http, ping, or even samba.
I just did a clean install of CentOS on the server, and everything is working fine when I connect to it from any of my Windows machines. However my Macbook won't connect any more. I can view my development versions of my websites in a browser, but I can't ssh in to the server.
I cleaned out
~/.ssh/known_hosts to make sure the old server's information wasn't mucking things up. How are the Windows machines and Mac browsers able to find the server, but Terminal can't?
~: ssh firstname.lastname@example.org ssh: Could not resolve hostname server.local: nodename nor servname provided, or not known ~: ssh email@example.com firstname.lastname@example.org's password:
I already tried flushing the DNS cache by
I'm on OS 10.6.
Ok, so why is Terminal confused about the domain name when browsers are not?
192.168.1.200 server.local to
/etc/hosts fixes the problem. I'm just wondering why it's not able to rely on the router's DNS.