diff --git a/packages/create-razzle-app/templates/default/README.md b/packages/create-razzle-app/templates/default/README.md
index e54a6b0eb..6c6124694 100644
--- a/packages/create-razzle-app/templates/default/README.md
+++ b/packages/create-razzle-app/templates/default/README.md
@@ -155,7 +155,7 @@ Last but not least, if you find yourself needing a more customized setup, Razzle
 * `process.env.REACT_BUNDLE_PATH`: Relative path to where React will be bundled during development. Unless you are modifying the output path of your webpack config, you can safely ignore this. This path is used by `react-error-overlay` and webpack to power up the fancy runtime error iframe. For example, if you are using common chunks and an extra entry to create a vendor bundle with stuff like react, react-dom, react-router, etc. called `vendor.js`, and you've changed webpack's output to `[name].js` in development, you'd want to set this environment variable to `/static/js/vendor.js`. If you do not make this change, nothing bad will happen, you will simply not get the cool error overlay when there are runtime errors. You'll just see them in the console. Note: This does not impact production bundling.
 * `process.env.VERBOSE`: default is false, setting this to true will not clear the console when you make edits in development (useful for debugging).
 * `process.env.PORT`: The `BUILD_TARGET=server` build listens on this port for all NODE_ENVs. default is `3000`
-* `process.env.HOST`: The IP address that the server will bind to. default is `0.0.0.0`, for INADDR_ANY
+* `process.env.HOST`: The IP address that the server will bind to. default is `localhost`, for INADDR_ANY
 * `process.env.NODE_ENV`: `'development'` or `'production'`
 * `process.env.BUILD_TARGET`: either `'client'` or `'server'`
 * `process.env.PUBLIC_PATH`: Only in used in `razzle build`. You can alter the `webpack.config.output.publicPath` of the client assets (bundle, css, and images). This is useful if you plan to serve your assets from a CDN. Make sure to _include_ a trailing slash (e.g. `PUBLIC_PATH=https://cdn.example.com/`). If you are using React and altering the public path, make sure to also [include the `crossorigin` attribute](https://reactjs.org/docs/installation.html#using-a-cdn) on your `<script>` tag in `src/server.js`.
diff --git a/packages/razzle/config/env.js b/packages/razzle/config/env.js
index 372b761be..4dc3b682e 100644
--- a/packages/razzle/config/env.js
+++ b/packages/razzle/config/env.js
@@ -51,7 +51,7 @@ function getClientEnvironment(target, is_dev, options, paths) {
         NODE_ENV: process.env.NODE_ENV || 'development',
         PORT: process.env.PORT || options.port || 3000,
         VERBOSE: !!process.env.VERBOSE,
-        HOST: process.env.HOST || options.host || '0.0.0.0',
+        HOST: process.env.HOST || options.host || 'localhost',
         RAZZLE_ASSETS_MANIFEST: paths.appAssetsManifest,
         BUILD_TARGET: target === 'web' ? 'client' : 'server',
         // only for production builds. Useful if you need to serve from a CDN
diff --git a/website/pages/docs/environment-variables.md b/website/pages/docs/environment-variables.md
index a10c16a1e..73b6d257c 100644
--- a/website/pages/docs/environment-variables.md
+++ b/website/pages/docs/environment-variables.md
@@ -9,7 +9,7 @@
 - `process.env.REACT_BUNDLE_PATH`: Relative path to where React will be bundled during development. Unless you are modifying the output path of your webpack config, you can safely ignore this. This path is used by `react-error-overlay` and webpack to power up the fancy runtime error iframe. For example, if you are using common chunks and an extra entry to create a vendor bundle with stuff like react, react-dom, react-router, etc. called `vendor.js`, and you've changed webpack's output to `[name].js` in development, you'd want to set this environment variable to `/static/js/vendor.js`. If you do not make this change, nothing bad will happen, you will simply not get the cool error overlay when there are runtime errors. You'll just see them in the console. Note: This does not impact production bundling.
 - `process.env.VERBOSE`: default is false, setting this to true will not clear the console when you make edits in development (useful for debugging).
 - `process.env.PORT`: The `BUILD_TARGET=server` build listens on this port for all NODE_ENVs. default is `3000`
-- `process.env.HOST`: The IP address that the server will bind to. default is `0.0.0.0`, for INADDR_ANY
+- `process.env.HOST`: The IP address that the server will bind to. default is `localhost`, for INADDR_ANY
 - `process.env.NODE_ENV`: `'development'` or `'production'`
 - `process.env.BUILD_TYPE`: `'iso'` for isomorphic/universal applications or `'spa'` for single page applications. The default is `'iso'`. This is set by CLI arguments.
 - `process.env.BUILD_TARGET`: either `'client'` or `'server'`