DNS doesn't resolve anymore under latest update.

Question

I am having this new problem. I have about 10 network interfaces. en0 ..... en10,en11. This is from working different locations with different Thunderbolt, USB 3.0 gigabit adapters. Each time I use a new adapter, a new network interface is created.
Now my DNS no longer resolves. I manually set my IP and DNS to 8.8.8.8. 8.8.4.4 (Google's DNS) which works in the past.
I can't ping anything. I can't get on the public internet.
I've deleted all the network interfaces in the GUI and in the terminal.
E.G. can't ping yahoo.com, google.com or apple.com
When I do nslookup like
bash-3.2# nslookup apple.com 8.8.8.8
Server:                    8.8.8.8
Address:          8.8.8.8#53
Non-authoritative answer:
Name:          apple.com
Address: 17.149.160.49
Name:          apple.com
Address: 17.178.96.59
Name:          apple.com
Address: 17.172.224.47
It resolves. But when I ping it, I get
bash-3.2# ping apple.com
ping: cannot resolve apple.com: Unknown host
Here is my /etc/resolv.conf
# Mac OS X Notice
# This file is not used by the host name and address resolution
# or the DNS query routing mechanisms used by most processes on
# this Mac OS X system.
# This file is automatically generated.
nameserver 8.8.8.8
nameserver 8.8.4.4
I can ping anything by IP address. I just access anything by DNS. I can access by IP.
I zapped my PRAM. I did the old trick of deleting all my network interfaces in /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist.
I removed my byhost file. rebooted.
Went into the GUI and deleted/disabled all the network interfaces.
I know just have en0, en1/en2 (Thunderbolt Bridge). I disabled en1/en2
I just have lo0,stf0,gif0,p2p0,en0 when I do ifconfig.
ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
          options=3<RXCSUM,TXCSUM>
          inet6 ::1 prefixlen 128
          inet 127.0.0.1 netmask 0xff000000
          inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
          nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
          ether xxxxxx
          inet6 xxxxx
          inet 192.168.0.54 netmask 0xffffff00 broadcast 192.168.0.255
          nd6 options=1<PERFORMNUD>
          media: autoselect
          status: active
en1: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
          options=60<TSO4,TSO6>
          ether xxxxx
          media: autoselect <full-duplex>
          status: inactive
en2: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
          options=60<TSO4,TSO6>
          ether xxxxxx
          media: autoselect <full-duplex>
          status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
          ether xxxxxxxx
          media: autoselect
          status: inactive
I create another user, logged in as that user and no-go.
I have 14 other machines on the network, I can set IPs manually or DHCP and they all work.
My Macbook Retina no longer works. I don't want to do a reinstall.
my /etc/hosts file is clean
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1             localhost
fe80::1%lo0     localhost
I've disabled IPV6 (set it to local link only).

Answer 1

IP is:
192.168.0.154 (or whatever DHCP or manual IP I set in 192.168.0.X)
Router: 192.168.0.1
Netmask: 255.255.255.0
DNS: 8.8.8.8, 8.8.4.4
I can ping the router, access every IP on my network. I can access public FTP servers by their IP. My mail server by IP.
Machines on the network can access my machine by IP.
The DNS can't resolve internally.
Crash.log shows mDNSResponder crashing every second. Seems it may be corrupt.
I've killed it, dscachecutil --flush(whatever the command was),
I killed it -9, -HUP, etc.
I've copied the plist and launcdaemons from another working macbook.
Interestingly, Chrome works. In the crash logs, when chrome sees the mDNSresponder failing, it uses something else and internally routes the DNS to a different proxy.
I can surf the web with Chrome. Chrome doesn't use mDNSResponder in the event of a failure. That is how I posted my question.
Nothing else works. Firefox, Safari, iTunes, AppStore, FTP clients, Command line terminal.
Is there a way to re-install mDNSResponder.