Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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 two VM, one is exchange server, and the other is client with outlook installed.
I can view the exchange server at at the client vm, and I want to set up a smtp server in exchange, which I can use it in the client vm,
Actually I don't have a domain, how can I set up a virtual domain, let's say smb.local, which enable the client to recognize it ?

then I can send email from client vm, with smtp server: smtp.smb.local ? How can I set this virtual domain?

share|improve this question
up vote 1 down vote accepted

For a simple use case, you don't need to do anything too special. Just be sure to configure (or smtp.smb.local) as the SMTP server from the client VM. If you want to use the hostname instead of the IP, you'll either need to setup DNS (below) or edit the hosts file of the client VM. However, I'm not sure that this will meet your request for setting up a "virtual domain".

For a more advanced case, you could setup at least a minimal DNS server so that you can serve the MX records necessary for a client looking at "smb.local", for example, to determine that your is configured to receive email for that domain (using smtp.smb.local - which must also be configured in DNS with an A record, resolvable, and reachable). Since you're already using a Windows Server for Exchange, you can use Microsoft's DNS server for this purpose. You'll also need to ensure that your client is setup to use this new DNS server as its DNS server for it to recognize this.

The entire setup for this really isn't any different than the normal setups for hosting a production email server with Exchange - so you can follow the regular Exchange documentation for configuring this. The only differences for a local / lab test is that none of the services - including DNS - need to be public, and that as such, the guest VM needs to be configured to use a test DNS server to find where things are at.

share|improve this answer
-1. I normally don't like to downvote, but an email client doesn't need to know, nor does it use the MX record for a domain. An email client connects to the email server that it is a client of, and that email server uses MX records to send email to non-local (non-authoritative) domains. – joeqwerty Dec 26 '11 at 3:15
@joeqwerty - You're right, I'll update the answer to reflect this, and hopefully yourself or someone else can leave a better answer. – ziesemer Dec 26 '11 at 3:16
Glad to help and glad you took my downvote in stride. Keep up your contributions to these questions. – joeqwerty Dec 26 '11 at 3:17
@joeqwerty - FYI, the OP did ask how to setup a virtual domain, for which these additional steps would be necessary. – ziesemer Dec 26 '11 at 3:21
How can I create a test DNS? – Hooligan Dec 26 '11 at 5:34

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.