Cannot Connect to Samba Shares on TrueNAS Server Via Domain
-
@johnpoz Here's the result with dig:
-
@n3IVI0 well why would you think 9.9.9.9 know anything about your local resources.. Do you own home.com, somehow I find that unlikely..
-
@johnpoz In the past, I only needed to specify a domain for LAN purposes. Then my clients could see it and connect to it.
-
@n3IVI0 well you were prob registering dhcp? I would not suggest you use some public domain like home.com - use something like the recommended home.arpa as your domain. Setup a dhcp reservation for your nas, or host override to point to its ip..
And you client can be asking 9.9.9.9 directly - since they are never going to have a clue about your local resources now are they.
-
@johnpoz Will home.arpa work for each device?
-
@n3IVI0 I use home.arpa for all my local resources - it is the recommended domain currently to use for local resources.
https://datatracker.ietf.org/doc/html/rfc8375
Special-Use Domain 'home.arpa.'And it is what pfsense currently defaults too.
You still need to have records for what you want to resolve.
-
@johnpoz That fixed it immediately. And as most things are when you have knowledge, it was easy to fix. Thanks for the tip!
-
@n3IVI0 Figured out what was causing all the trouble. I had switched to Kea DHCP. Switched back to ISC DHCP, told it to stop nagging about the deprecation, then I could go into DNS Resolver and tell it to register all my static DHCP leases in the DNS Resolver. Zip. Suddenly my shares were back, and could be seen in Network again. Thanks for the help.
-
@n3IVI0 no problem glad you got it sorted, so your dhcp being kea was also handing out 9.9.9.9 to your clients for dns?
-
@johnpoz Looks like. Dig looks different. Getting through to the domain like it used to. That's the thing that changed that FUBAR'd it. I changed to Kea.
