Local (LAN) domain confusion

[pastic]

I don't know if this belong here in DNS or in the Routing subforum.

I am calling my LAN nibelheim and my pfsense fafner. I can access pfsense at https://fafner.nibelheim.
I am calling my Truenas truenas and have configured its domain as nibelheim but I cannot access it at https://truenas.nibelheim.
For some reason I can access it at https://truenas.local

What could be going on?

[johnpoz]

@pastic did you create a record (host override) in your pfsense dns to resolve truenas.nibelheim to its IP? Or enable dhcp or static registration.

BTW, single label tld like just nibelheim not really a good choice.. how about nibelheim.lan ? .lan is a tld that should never really be used in the public dns..

.local is used by mdns.. So you finding it with truenas.local is using mdns to resolve the name... Which is just a broadcast a client sends out on 5353 with the name and clients with that name answer.

My nas is setup with the new recommended local domain home.arpa, and it also still resolves to its old domain local.lan that I am in the process of retiring

$ dig nas.home.arpa +short
192.168.9.10

$ dig nas.local.lan +short
192.168.9.10

https://www.rfc-editor.org/rfc/rfc8375.html
Special-Use Domain 'home.arpa.'

[pastic]

@johnpoz I have always had a static registration for truenas at 10.0.0.50 in pfsense. I had not entered a host override. Now it works. Thanks!

1. I guess I still don't grasp though, why, when pfsense configures my LAN as 10.0.0.1/24 and calls this domain .nibelheim and I have a static registration at 10.0.0.50 for truenas, why pfsense could not figure out the truenas.nibelheim is the same thing as 10.0.0.50?

2. So that truenas is findable with .local was simpy due to the fact that Truenas is broadcasting mDNS?

3. your suggestion to use nibelheim.lan, is that due to any practical disadvantages, or simply the fact that my LAN does not have a tld and that conceptually it is better to have one?

[Bob.Dig]

@pastic said in Local (LAN) domain confusion:

and I have a static registration at 10.0.0.50 for truenas, why pfsense could not figure out the truenas.nibelheim is the same thing as 10.0.0.50?

Have you checked your static registration?
Are you trying this from a LAN with pfSense as the DNS-server?

[pastic]

@Bob-Dig the static registration is fine:

Are you trying this from a LAN with pfSense as the DNS-server?
From a LAN yes, but perhaps pfsense is not my DNS server? I point it towards OpenDNS. However, I thought that only applied to non-LAN lookups.

[johnpoz]

@pastic did you set unbound to register your reservation?

as to using a single label.

https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/single-label-domains-support-policy

They are not good practice..

SLDs aren't a recommended configuration for future deployments and may not work with some products or versions. Other Microsoft or third-party applications that end users may want to run in your environment may not be compatible on an SLD. We recommend that customers deploy their infrastructure by using common, tested configurations to minimize extra deployment and testing costs.

You can run into problems.. Like I said I would suggest you not use a SLD.. But you do you.. Its difficult for search suffixes and can be problematic.

[pastic]

@johnpoz said in Local (LAN) domain confusion:

did you set unbound to register your reservation?

Oh... had not done that. Now it works without host override!
Thanks!