I have a MacBook Pro and I share its Ethernet connection to my iPhone and iPad as well as other wireless devices (enabling Internet Sharing in the Sharing preferences). However when I check on my iPhone what DNS it hands out, it shows Should that be? That's not any actual DNS server, that's something local to the network. It's not even the home router, something about the Mac I think.

In the past I had problems where I couldn't use the Internet on the devices that were connecting to the shared WiFi unless I manually set the DNS server on each wireless device (not the Mac) to some actual server like That was a workaround for my iDevices that let me make that change but not for other devices.

I've upgraded my OS to El Capitan since I made those initial observations, but I checked again and it is still putting out that same DNS server. I'm not sure if the Internet still wouldn't work on other devices since I'm not using them. But is that the right IP?

If relevant, here is my Ethernet settings: Network Preferences

1 Answer 1


...when I check on my iPhone what DNS it hands out, it shows

What you are seeing is completely normal.

To verify this, I setup Internet Sharing over WiFi with my Ethernet adapter as my primary connection and got the exact same results you did (the IP addresses varied some, but it's irrelevant).

I even tried it on a Windows Phone - here's the screenshot of the settings the phone got from my iMac:

enter image description here

When you enable Internet Sharing, it turns your Mac into a DHCP server and DNS forwarder - basically, it turns into a router along with NAT and firewall services to boot.

The IP address that you are seeing - - is the bridge interface on your Mac. It's what bridges the connection between the Wireless LAN you set up in Internet Sharing and your physical Ethernet adapter.

Executing ifconfig in Terminal brings up the following:

    ether a8:20:66:39:2c:1c 
    inet6 fe80::aa20:66ff:fe39:2c1c%en0 prefixlen 64 scopeid 0x4 
    inet netmask 0xffffff00 broadcast
    nd6 options=1<PERFORMNUD>
    media: autoselect (1000baseT <full-duplex,flow-control,energy-efficient-ethernet>)
    status: active
    ether 8c:2d:aa:3a:ec:83 
    inet6 fe80::8e2d:aaff:fe3a:ec83%en1 prefixlen 64 scopeid 0x5 
    inet netmask 0xffff0000 broadcast
    nd6 options=1<PERFORMNUD>
    media: autoselect
    status: active

    ether aa:20:66:93:de:64 
    inet netmask 0xffffff00 broadcast
    inet6 fe80::a820:66ff:fe93:de64%bridge100 prefixlen 64 scopeid 0xc 
        id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
        maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
        root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
        ipfilter disabled flags 0x2
    member: en1 flags=3<LEARNING,DISCOVER>
            ifmaxaddr 0 port 5 priority 0 path cost 0
    nd6 options=1<PERFORMNUD>
    media: autoselect
    status: active

If you notice, there is now a bridge100. This is a virtual interface that was created on the WLAN adapter. If you execute that command in your Terminal, you should get something similar.

As for your DNS, what is happening is that your phone/tablet will send the DNS request to your Mac, and then your Mac will take that request and send it to the DNS hosts you have listed. When the response comes back, your Mac will pass it along to the wireless client that made the request.

I also tested browsing the Internet and fetching mail - all worked with no problem. I am running El Capitan 10.10.5

Are you having that problem now?

  • Thank you. I don't appear to currently be having issues connecting over the WiFi even after I remove custom DNS settings from the mobile devices. I will have to see how it goes over time though, because in the past (Mountain Lion and Lion) it was a little sporadic.
    – kal-al
    May 25, 2016 at 23:24
  • No problem. Sorry about the first answer I was multi-tasking (I shouldn't do that) I was trying to see if there was a bug in previous versions, but couldn't find anything.
    – Allan
    May 25, 2016 at 23:29
  • 1
    @kal-al: You are perfectly right. The problem continued with the first versions of Yosemite. But I can insure you that Apple fixed completly their DNS cache engine now (see mDNSResponder).
    – dan
    May 25, 2016 at 23:29
  • @Allan: "into a router of sorts" → "into a router". In fact as you perfectly stated it provides the services of a DHCP server, a DNS forwarder, but also of a NAT server and a firewall.
    – dan
    May 25, 2016 at 23:37
  • 1
    If you want to insert any piece of information of my answer, please do. It will self destruct within 5 minutes :).
    – dan
    May 25, 2016 at 23:48

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .