Discoveryd Basic Sockets Couldn't set IP_BOUND_IF on socket fd[72] scopeID[4] errno[22] result[-1]

Question

message loop filling system log.
Text: discoveryd Basic Sockets Couldn't set IP_BOUND_IF on socket fd[72] scopeID[4] errno[22] result[-1]
Value of fd[] does cycle
Loop prevents access to internet
Tried work-around from http://apple.stackexchange.com/questions/153080/computer-name-keeps-changing-osx -10-10-14a389
Basely has an affect.
Power-off of router stops the loop.
Powered-off for 5 (five) minutes and can access internet
Macbook Air (MBA) and iMac both experience the loop

Answer 1

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.