Posted this on StackOverflow, but I think it's probably more germane to this crowd.

I am having an issue with sending a MSMQ message to the second DNS name on a server. If we send the IP for that same server, we're fine, but that's not where we are going architecturally. Any ideas as to why MSMQ would care about which name it receives?

Here is our example:

Server Information: The physical server load-int-01, has a second IP and DNS name associated with it. First IP/DNS: `load-int-01`, with IP `10.0.10.10` Second IP/DNS: `load-intv`, with IP `10.0.10.20`

Queue path formats used:

`FormatName:DIRECT=OS:load-int-01\private$\MyQueue` -> Works Fine 

`FormatName:DIRECT=OS:load-intv\private$\MyQueue` -> Returns the following error:

> 
> The queue does not exist or you do not have sufficient permissions to perform this operation
> 
> 
> 

We have also tried using the IP addresses instead, and both sets of IPs work fine.

`FormatName:DIRECT=TCP:10.0.10.10\private$\MyQueue` -> Works Fine `FormatName:DIRECT=TCP:10.0.10.20\private$\MyQueue` -> Works Fine