Ok this is a bit confusing sorry, but lets try to isolate because this seems like something that is caused by your actual network configuration and not screenly…
I am using a screenly image so there is no actual interface to the device. I disabled ipv6 on my Comcast router. I traced this as what was handing out the dhcp.
When you say no actual interface, you mean you cant access the screen with keyboard and mouse? This is true that screenly doesn’t have interface, what I meant was network interface file, but you can access the console by pressing
ctrl+alt+f1 on the keyboard connected to the Pi and it should bring up the console screen asking you to log in with default login (pi/raspberry).
You say you disabled Comcast because it was sending out ipv6 dhcp addresses, how was the Pi connected to the network in the first place? Ethernet or WiFi? because for you to get an IP from your Comcast router it must have been connected to it one way or another.
Do you want to configure it for WiFi or Ethernet?
There are a few ways to get the network configured, one easy way is first connecting to Ethernet and as you saw, the screen will show the IP it obtained on the screen, then you should be able to access that IP from a computer on the same network that allows communication between local subnets.
Reason I say this is because if you are on a network that uses a guest configuration, it probably does not allow communication between local devices and only to outgoing. This will prevent you to access the Pi if you tried to access that IP by putting it in the browser as URL.
If you are not able to ping that IP that you saw on the screen, then that is a problem that needs to be resolved on the network router first, or else you wont be able to access the screenly viewer/server to configure it.
This part confused me as well:
My other option, which I am hesitant to do, is enable dhcp ipv4 on my domain controller. We have all static here now.
If you have static IP, how did it get a ipv6 via DHCP earlier on?
Will you be using the Pi in a DHCP or Static IP environment?
After you have resolved the network issue, and you want to enable SSH for future remote access and configuration, here is an alternative easy way if you have physical access to the Pi:
Mount the SD card to a computer
Go into the /boot/ partition
Create an empty file and name it ssh or ssh.txt (case sensitive)
That's it, that system will now have SSH enabled when booted
please change the password from the default once you have SSH enabled
passwd in console.
Remember root and pi should both get password changed, so typing passwd only changes it for the user that executes the command, you should also do
sudo passwd so that it changes the password for root.