Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a computer in my house set up at, say <domname>, it also has a local IP of Is it consistently faster to use <domname> or the IP for SSH (when working inside the home network)? What about for other projects (say as a web server)?

share|improve this question
If the difference is noticable, you need to fix your DNS config! – RedGrittyBrick Nov 30 '11 at 11:52
I didn't notice a difference, but that doesn't mean that there wasn't one! – cwallenpoole Nov 30 '11 at 13:53
up vote 2 down vote accepted

It is never faster to use a DNS name than an IP address no matter what the scenario. If you use a DNS name, a lookup has to occur to get the IP address. This takes time that would not be necessary if using the IP address directly.

Having said that, for all manner of reasons, it is generally best to use a DNS name whereever possible (and incur the cost of this lookup), as it means the IP address can change without reconfiguring anything else. Of course you would need to be sure your DNS servers are robust as they become a point of failure.

Convenience is another reason, particularly if you have machines such as a laptop that might be on the internal network and the external network. If you can use DNS then your usage is the same inside and outside of the network.

Lots of domestic routers don't support accessing a public IP address that is portforwarded from the same network it is forwarded to, so take advantage of it if yours lets you.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .