The names you see
looks like hostnames and not bonjour names.
As i understand it you
- have a mac mini with two NIC´s (Network Interface Card)
- both o which are connected to the same subnet
This would mean that the hostname of your mac mini, mac.local, is causing a conflict on your network,
this conflict results in one of the NIC´s to take another name than "mac.local". The usual behaviour here is to
add a number at the end of the hostname - "mac-1.local"
192.168.1.120 <---- ethernet --[ MacMini ]-- wifi ----> 192.168.1.121
The mac mini is called "mac.local", since both NIC´s are connected to the same subnet (192.168.1.x), it may lead to other unexpected behavior.
You could try this as a possible work around:
Set up second router between your ethernet NIC and the original subnet, and open the ports you need for the services you need to access on that sepciffic NIC
192.168.1.120 <----[ router ] 10.0.1.12 <---- ethernet --[ MacMini ]-- wifi ----> 192.168.1.121
Please tell me if i have misunderstood the problem and i will try to provide you with a better solution
Yes, you are correct about this.
The Multicast DNS feature of Bonjour technology allows devices on a local network to connect to each other by name without a separate DNS server, this adds the ".local" to the end of the hostname.
A really nice feature about this is if a host suddenly looses its IP, and gets a self-assigned IP instead, it can still be reached by its bonjour name.
Still, if connecting two NIC´s from the same host to the same subnet, you will get the issue you described here.
Had the same issue a while back, took me a lot of googeling to figure out why it kept renaming my host
If you connect multiple NIC´s to the same subnet, it will automatically rename one of them to *-1.local
I know its possible to edit the /etc/hostname.[ interface name ] in *NIX like platforms.
Even if Mac OS X is a *NIX like platform i have seen, more than once, that Apple has applied their own special touches and one of this is the abcence of /etc/hostname.
Sorry to say; i have no idea if you could edit any system files in Mac OS X to solve that.
I think that topic would be something that you could get answered in the the OS X server forum maybey?