You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

WiFi Static IP Address Requires DNS Server

I have been able to confirm this on two separate MacBook Pros (different models) both running Yosemite 10.11.4.


After assigning a static IP address to the wireless network interface, the MacBook won't ping an address beyond the default gateway unless there is also a DNS server assigned on the wireless interface. I shouldn't need a DNS server to ping a public IP address.

For example:

This works.

User uploaded file


But this doesn't work:



User uploaded file

User uploaded file


Unless I change the DNS like this:


User uploaded file


Then it will start working again.


I tried running a packet capture and the MacBook doesn't even send ping requests out the wireless interface unless there is a static DNS server assigned.


Can anyone else confirm/deny this behavior for me?


Thanks,

Rob

MacBook Pro, OS X El Capitan (10.11.4), Wireless adapter bug?

Posted on Apr 12, 2016 2:08 PM

Reply
7 replies

Aug 21, 2016 8:14 AM in response to richeyrobert

Hi,


I have found the same issue as you and I totally agree with you that it should work without a DNS.

As a network administrator, there are many scenarios in which this is useful.

I found that in the scenario where you don't have a DNS configured and no routing is working but that "netstat -nr" does show a default gateway, if you 're-add' the default gateway (sudo route add default ROUTER_IP), then it starts working. However, there is still no DNS and the routes are still the same!

I totally consider this as an issue! However, I do not know if it's on Apple's side or if it is the same behaviour on BSD.


Thanks for reporting that "Question", it really helped me find that I wasn't the only one and that I don't have an issue with my system...

Regards,

Maxime

Apr 12, 2016 3:50 PM in response to richeyrobert

I do understand what you have written. But I don't run without DNS configured and wouldn't suggest it, and I don't know your network configuration.

IP routing can sometimes have results other than those intended, particularly when there are multiple NICs present and active.

But in any case, please report this to Apple formally.


FWIW, DNS is no longer optional, it's part of the foundation of modern IP networks.

Apr 12, 2016 2:20 PM in response to richeyrobert

What exactly are you trying to do?


Are you trying to assign a Mac with a LAN static IP address? If so, do it within the router by selecting an IP Address on the LAN to use with the Machine Address (MAC Address) of the Mac. This assumes your router is your DHCP server. Otherwise, you need an DNS server that has DHCP running on your LAN to be able to hand out IP addresses.

Apr 12, 2016 2:27 PM in response to keg55

That's a great idea keg55, but I need to be able to assign my wireless adapter a static IP Address on-the-fly (hopefully without putting in a DNS server address). So updating the address in the router won't work for my application. I need to know if this is just a problem on my network of if this is a bug/limitation on OS X. It will work just fine on a wired connection, but on a wireless connection I can't get it to work the same.

Apr 12, 2016 2:37 PM in response to richeyrobert

You got me!


I have only assigned static IP addresses on my LAN via my router for a wired server and my WiFi printer. I don't have the same need as you to be able to change them to different addresses from time to time. I only have basic knowledge as far as networking goes, sorry.


I guess I don't understand why you want to be able to use ANY IP address instead of the IP addresses assigned on the network you're connecting to.

Apr 12, 2016 2:40 PM in response to richeyrobert

I don't know how much you know about IP and routing, so the following might be a review, or it might be new. I also don't know if the AirPort or Time Capsule is the sole NAT device here, or if there might be a second device running NAT. Apologies here, but I just can't see your config.


Depending on how your network is wired, are your wired connections and your Wi-Fi connections in different subnets or your Wi-Fi configured as an access point? Because if not separate subnets, there can be routing problems. This particularly when there are multiple links active. To avoid routing problems, you'll want separate subnets for wired and wireless with the Wi-Fi operating as a router, or your Wi-Fi configured as an access point and the same subnet across both wired and wireless; what Apple refers to as bridging.


Where are you performing the packet capture here? With Wi-Fi, that only works "upstream" of the Wi-Fi (access point or router) device, as other devices on the Wi-Fi won't pick up the traffic.


And while I understand what you've asked for here, OS X and most systems want and beed DNS for (among other reasons) network security — it's very unusual to try to run without DNS servers involved somewhere. It'd be helpful to understand a little more about why you're trying to run without a DNS server, and how your network is set up.

Apr 12, 2016 2:55 PM in response to MrHoffman

I am performing the packet capturing on the wifi interface. With a DNS server assigned, I can see the ping echo requests and responses. Without the DNS servers assigned, I can't see any ping echo requests or responses in WireShark (for any IP address that isn't on my local network).


This would lead me to believe that the operating system isn't sending any ICMP packets to non-local destinations out the interface unless there is a DNS server assigned.


As a simple test, you could assign a valid IP address to your wireless adapter, remove the DNS servers and see if you can ping a public IP address (like google's DNS server at 8.8.8.8) to see if you have the same problem that I do.


I understand that most (if not all) systems want DNS, but if I don't supply a DNS server, I should technically still be able to ping a public IP address. It works fine with a dynamically assigned address, therefore it would follow that a statically assigned IP address would work equally.


Does that make sense?

WiFi Static IP Address Requires DNS Server

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.