resolv.conf on BB Black Rev C / Debian

I finally got my BB to ping 8.8.8.8 through my windows 10 laptop BUT I cannot modify resolv.conf to add the name server for www.google.com.

in directory /etc resolv.conf is shown in red, what does this mean? typing more resolv.conf gives ‘no such file or directory’

Is there a different way to resolve names using the BB Black Rev C running Debian?

On Sun, 1 Sep 2019 12:19:29 -0700 (PDT), Brian Tremaine
<btremaine@gmail.com> declaimed the
following:

I finally got my BB to ping 8.8.8.8 through my windows 10 laptop BUT I
cannot modify resolv.conf to add the name server for www.google.com.

in directory /etc resolv.conf is shown in red, what does this mean? typing
more resolv.conf gives 'no such file or directory'

  Since I edit my profiles to disable color coding of file/directory
types, saying something is "red" is meaningless... What does "ls -l" show?

drwxr-xr-x 4 root root 4096 Oct 7 2018 resolvconf
lrwxrwxrwx 1 root root 24 Oct 7 2018 resolv.conf ->
/run/connman/resolv.conf

mine shows a link to a different file...

debian@beaglebone:~$ ls -l /run/connman
total 4
-rw-r--r-- 1 root root 80 Sep 3 14:20 resolv.conf
debian@beaglebone:~$

... and that file is essentially read-only

debian@beaglebone:~$ cat /etc/resolv.conf
# Generated by Connection Manager
search attlocal.net
nameserver 192.168.1.254
debian@beaglebone:~$

  Note the first line -- editing the file likely won't help, it get
recreated on each boot. (I'm wired directly to my router, and my router
provides the first layer of nameserver response -- I don't run ICS so using
USB-only won't get anywhere).

  Booting without the cat-5 cable, indicates that the file is not created
at all... And this bit

https://support.microsoft.com/en-us/help/324286/how-to-set-up-internet-connection-sharing-in-windows-server-2003
"""
The ICS computer automatically assigns IP addresses, forwards DNS names to
the Internet for name resolution, and assigns itself as the default gateway
for connections to the Internet. If the ICS-enabled computer is
unavailable, the other client computers on your network cannot access the
Internet.
"""

seems to indicate a possible problem. ICS may want to run as DHCP for the
clients (ie: providing IP and gateway information) -- but the RNDIS (USB)
connection uses fixed IPs provided by the Beagle.

  Compare with ICS active:

BBB
usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.7.2 netmask 255.255.255.252 broadcast 192.168.7.3

vs Win10 with ICS
Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix . :
   IPv6 Address. . . . . . . . . . . :
2600:1700:e630:89f:a10d:c6b2:4a61:19f8
   Temporary IPv6 Address. . . . . . :
2600:1700:e630:89f:c9ef:7900:8cbc:f44d
   Link-local IPv6 Address . . . . . : fe80::a10d:c6b2:4a61:19f8%15
   IPv4 Address. . . . . . . . . . . : 192.168.137.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Note how ICS attempted to give a 192.168.137.* to the interface, but the
BBB still thinks the link is 192.168.7.*

  In contrast, with ICS turned off on the Win10 machine... and rebooting
the BBB...

BBB:
usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.7.2 netmask 255.255.255.252 broadcast 192.168.7.3

Win10:
Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix . :
   Link-local IPv6 Address . . . . . : fe80::a10d:c6b2:4a61:19f8%15
   IPv4 Address. . . . . . . . . . . : 192.168.7.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.252
   Default Gateway . . . . . . . . . :

...both ends are in the 192.168.7.* "network"

  I don't plan to fiddle deeper -- I suspect it may require changing the
BBB usb0 inet/netmask/broadcast values to be in the ICS range (and hope
that doesn't change from boot to boot on either end).