Skip navigation

VMWare Fusion Adapters Register in DNS

1690 Views 6 Replies Latest reply: Apr 7, 2013 7:47 PM by chymb RSS
OLDGUARDMD Calculating status...
Currently Being Moderated
Sep 4, 2012 7:30 AM

Our MAC systems are running Mac OS X version 10.6.8 with VMWare Fusion. We have noticed that these boxes all contain DNS entries for the virtual adapters associated with VMWare Fusion. Can someone shed some light on how Dynamic DNS registration happens on OSx 10.6.8? I have seen references to modifying the smb.conf file isolate the adapters, but that appears to have had no affect. I am not even sure Samba is involved at this point. We would like to restrict Dynamic DNS registration to just en0. The adapters that appear to be causing the problem are vmnet1 and vmnet8.

 

We have tried modifying the last lines of the smb.conf global section to include the following:

 

  interfaces = eth0

    bind interfaces only = yes

 

This appears to have no impact on the registrations. The key questions here are:

 

How does OS X decide which adapters to register?

Is Samba the process that performs the registration?

Is the behavior configurable so we can exclude vmnet1 and vmnet8 from Dynamic DNS registration?

 

Additional Information:

  • Systems are part of a Windows domain
  • DNS Servers are AD integrated Windows 2008 R2 servers.
Mac mini
  • MrHoffman Level 6 Level 6 (11,720 points)
    Currently Being Moderated
    Sep 4, 2012 11:02 AM (in response to OLDGUARDMD)

    Windows Server DNS implements a connection between DHCP requests and DNS services; check with the Microsoft Windows Server documentation for details of that.  Here's how to implement Dynamic DNS (DDNS) on OS X Server.  Whether VMware itself gets involved here (and it may), I don't know.

     

    Follow the DHCP reservations around; that's the most likely path for this stuff.

     

    SMB (a port of the Samba server, on this OS X release) is a Windows-specific file and disk storage service, and not particularly connected with DNS or DHCP operations.

  • timeOday Calculating status...
    Currently Being Moderated
    Feb 5, 2013 1:19 PM (in response to OLDGUARDMD)

    I have the same problem and wanted to thank you for the helpful suggestion.

     

    One caveat is that (at least for a NAT'd guest) I don't see any way to address the guest, so it can't run server processes.  Applications on the host cannot route to the guest because they don't see a NIC on its subnet.  So you cannot export a file share from the guest, or ssh into it, etc.

  • chymb Calculating status...
    Currently Being Moderated
    Apr 7, 2013 7:47 PM (in response to OLDGUARDMD)

    This worked for me (on Mountain Lion, anyway):

     

    http://support.apple.com/kb/ht3169

     

    On (Mountain) Lion:

    dsconfigad -restrictDDNS "en0, en1, en2, en3, en4, en5, en6, en7, en8, en9"

     

    On (Snow) Leopard add the following lines to the end of /etc/smb.conf:

    [global]

    interfaces = en0 en1 en2 en3 en4 en5 en6 en7 en8 en9

    bind interfaces only = yes

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.