title: Registering Multiple Same-Host Services
body: <p>I am using <a href="https://www.consul.io/api/agent/service.html#register-service" rel="nofollow noreferrer">the Consul API</a> to register a local web-service running on various ports on my local machine. My end-goal is to be able to run multiple backends and load balance against them on different ports.</p>
  
  <p>I am running a local Consul server of one node for development in a Vagrant VM. I have registered the first instance of my service:</p>
  
  <pre><code>{
    "Node": {
      "ID": "49d3be4b-5ee5-5f0f-e145-dcb1782e5b4b",
      "Node": "localhost",
      "Address": "127.0.0.1",
      "Datacenter": "dc1",
      "TaggedAddresses": {
        "lan": "127.0.0.1",
        "wan": "127.0.0.1"
      },
      "Meta": {
        "consul-network-segment": ""
      },
      "CreateIndex": 5,
      "ModifyIndex": 6
    },
    "Services": {
      "consul": {
        "ID": "consul",
        "Service": "consul",
        "Tags": [],
        "Address": "",
        "Port": 8300,
        "EnableTagOverride": false,
        "CreateIndex": 5,
        "ModifyIndex": 5
      },
      "rusty": {
        "ID": "rusty",
        "Service": "rusty",
        "Tags": [
          "rusty",
          "rust"
        ],
        "Address": "127.0.0.1",
        "Port": 8001,
        "EnableTagOverride": false,
        "CreateIndex": 247,
        "ModifyIndex": 491
      }
    }
  }
  </code></pre>
  
  <p>You can see my service, <code>rusty</code>, registered on port 8001. The strange thing is that when I register the same service on a different port, Consul supersedes port 8001 with the new service port.</p>
  
  <p>Is there not a way to run multiple backends for a service on different ports on the same host?</p>