Server Fault is a question and answer site for system and network administrators. 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'm following a tutorial to set up vagrant (a tool to build and configure portable virtual machine images), and it seems that vagrant documentation suggests using IPv4 address to configure a new box.

That is a publicly routed IP adress, so I'm a bit confused why using this address is suggested. Since I don't own this network, I should not use an address from the range. Am I correct in thinking that I should only use either a public address from a network I own, or an address from one of the private ranges as defined in RFC 1918? If so, why does Vagrant documentation suggest otherwise?

share|improve this question
up vote 3 down vote accepted

The vagrant documentation does not appear to suggest to use

Digging deeper into the official documentation, I was only able to find RFC 1918 addresses in use.

Given the apparent close association between Vagrant and this incorrectly-used address, I can only surmise that the docs did refer to it in the past, and were later corrected.

Oh, and you definitely should not use someone else's public IP address, even on your own private network. Very Bad Things can (and probably will) happen.

share|improve this answer

As to why they've suggested you do it I'm going to go with "they're idiots". But really that's something we can't answer here. Why do people say or do anything? You'd need to ask the person who wrote that documentation.

As to what you should do, you're absolutely right: You shouldn't be using public IP addresses you don't own.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.