DNS Server keeps changing to 10.0.22.1 & .2 in OSX 10.9

dnsNetwork

My DNS Server keeps changing to 10.0.22.1 & 10.0.22.2 in OSX 10.9.5. This causes me to regularly lose internet access until I go into the network preferences pane and delete the two "incorrect" DNS address which cause the correct addresses to automatically re-appear. Then after re-starting my browser, all is well again. If I check my network settings again, the incorrect DNS address have almost always re-appeared by themselves but loss of internet hasn't necessarily occurred. I've checked the DNS settings in my Apple Airport and they are correct and haven't changed and I've also cleared all caches but that doesn't seem to make a difference.

Please HELP!

Best Answer

I discovered that the VPN that I'm running (ProXPN) changes the DNS settings to the ones I mentioned in my original post when I enable it thru its own software. I contacted their tech support who confirmed this. The VPN does not allow me to specify my own settings or disable the settings it loads. They explained that their DNS server is "secure." They also said that their settings are supposed to return to normal when disabling the VPN. Unfortunately they do not. So in the mean time, when I disconnect from the VPN, I have to go into the network pref pane and manually delete the VPN-set DNS addresess at which point, the correct ones appear automatically.

Tech Support said, "They'd look into it."

Thanks everybody for your input. I'll post anything if ProXPN Tech Support comes up with a solution.

JAY

Related Solutions

MacOS – AirPort Extreme: Keep IP address from changing

Your External IP Address (or, as you call it, the IP address reported by whatismyip.com) is not under your control and you can't simply set it to static. Your ISP gives you a new one when you reconnect, although there are chances that you might get the same, you should never count on it.

In order to solve this problem you have two choices:

Some Internet Service Providers (ISPs) offer you a "Static" IP service for a monthly fee. With the lack of IPv4 in the world, this service is unlikely to exist forever to individuals and it's usually reserved for companies and services that really need a static IP. Not all the ISPs offer this, you can always ask.
Use a Dynamic DNS provider. This will mean that although your IP address will eventually change when you disconnect (or your provider wants), you will always be able to get "back" to your Airport's IP by using a "name" rather than an IP. Any computer in your network will have a small piece of soft (some routers can do this automatically, I'm not sure about Airport Extreme, don't think so), that will periodically check your IP and if it has changed, it will inform the Dynamic DNS service that you use so it can update the value.

Some Dynamic DNS Providers (Mostly a free service) are (in no particular order):

DynDNS
No-IP (I use this)

Think of this as if instead of having a fixed phone number (static ip), a person could call you by "name" and the phone will check what is your current number (wouldn't that be great? ;) Nobody knows your number, only your name, because your number changes often (your ip!).

You haven't mentioned why you need a Static IP in the first place, but if you can't get it via your ISP, your only hope is to use Dynamic DNS. For what is worth, DDNS works really fine and it's very "fire and forget". Once it works, you no longer have to worry about IPs or anything, you just connect to: XXXXX.no-ip.org (for example)

MacOS – DNS not resolving on Mac OS X

It turns out the solution was to bounce mDNSResponder:

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist

This was obtained by a different coworker from this Server Fault question.

OS X 10.10.0 – 10.10.3, Yosemite

Apparently, mDNSResponder doesn't exist in Yosemite (OS X 10.10). You can restart descoveryd instead to fix these issues.

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist

OS X 10.10.4+, Yosemite

In OSX 10.10.4 the mDNSResponder has been reintroduced. So use the first one will work again.