The issue I am facing: Using hostname instead of IP to remote to share folders is not possible. I get a network error message. Only when using the IP address or adding the hostname to the Local DNS Records, am I able to use the hostname for remoting to shared folders on my LAN.
Details about my system: Windows shared folders. Android mobile devices.
What I have changed since installing Pi-hole: I had to manually add hostnames and their IP's to the Local DNS Records in order to access shared folders/assets.
Using an Android app called FX file explorer.
The app can access my shared folder via LAN to stream content to my TV.
I use the network search function to look for devices in my LAN.
It sees my PC as Gil-PC.
I add it, I add username and password and click connect.
The app supports SMBv1 and SMBv2+. I use SMBv2+.
I get an error: A network error occurred.
I used Telnet android app with the same hostname and port #445 to see if this is an isolated issue with the app.
I got similar error message.
I then replaced the hostname (Gil-PC) with the actual IP of the hostname and I was able to access my remote folder using FX explorer and established connection using Telnet.
Then, in Pihole I add my PC's hostname and IP address under Local DNS Records.
Using FX file explorer, I reverted the IP address to the hostname of my PC and I was able to connect successfully.
Given I encounter other LAN issues, I figured that I need to manually add all hostnames and their IPs to the Local DNS Records.
Another example is:
My LG TV can access my mobile devices media files (iOS/Android) using the LG ThinQ app as a casting service. Ever since I started using Pihole, I'm no longer able to access my mobile devices unless I set my router to not use Pihole as a DNS.
Is there an automated way of doing this when a new device is added to my network?
I thought that the Conditional forwarding under DNS settings handles that automatically.