BUG: wrong domain name

[n3gwg]

Andy, Andrew, et alia:

It seems that both the /etc/issue file as well as the /etc/update-motd.d/50-pistar-motd files instantiate the wrong domain name. They (for some reason) have ".local" hard coded there within, but my pi-star has a real domain name which can be displayed with the domainname command. Is there a way this can fixed in the future so that files that display the domain name get it right instead of presuming ".local" which is wrong for my network?

I'd recommend changing ".local" to "$(domainname)" in the 50-pistar-motd file at minimum, and then seeing how to propagate that out to /etc/issue as well.

My father always used to say, never assume and we all know why. However, if you presume you ought to be fine!

[MW0MWZ]

.local is exactly in relation to mDNS / Avahi and is correct for that use, and that use only.

[n3gwg]

.local is exactly in relation to mDNS / Avahi and is correct for that use, and that use only.

Andy,

Again, a cryptic answer that does not really make technical sense and that is quite odd from someone who is quite obviously extremely technical.

I know what Avahi is (an mDNS implementation) and what it is supposed to be doing. What I am curious about is as follows hereupon:

If mDNS is supposed to resolve hostnames then there must be a bug in Pi-Star or Avahi, as I use a network domain name different from ".local" and Pi-Star and Avahi are not taking notice of it. Surely that is not correct when the goal of Avahi is to detect the state of the network. Moreover, I also do have a DNS server on my network (pfSense integrates that for all DHCP based requests), so again, why is not being picked up properly by Pi-Star?

When I attempt to ping the hostname with ".local" attached to it, this fails, something is clearly broken. Do you not think that the most gain for Pi-Star users (and perhaps Avahi users if the bug is found to be within Avahi) would be to figure out where the bug is instead of just insisting nothing is broken when the functionality is not proper?

Thanks!

[MW0MWZ]

.local is exactly in relation to mDNS / Avahi and is correct for that use, and that use only.

Andy,

Again, a cryptic answer that does not really make technical sense and that is quite odd from someone who is quite obviously extremely technical.

I know what Avahi is (an mDNS implementation) and what it is supposed to be doing. What I am curious about is as follows hereupon:

If mDNS is supposed to resolve hostnames then there must be a bug in Pi-Star or Avahi, as I use a network domain name different from ".local" and Pi-Star and Avahi are not taking notice of it. Surely that is not correct when the goal of Avahi is to detect the state of the network. Moreover, I also do have a DNS server on my network (pfSense integrates that for all DHCP based requests), so again, why is not being picked up properly by Pi-Star?

When I attempt to ping the hostname with ".local" attached to it, this fails, something is clearly broken. Do you not think that the most gain for Pi-Star users (and perhaps Avahi users if the bug is found to be within Avahi) would be to figure out where the bug is instead of just insisting nothing is broken when the functionality is not proper?

Thanks!

Forgive me, not trying to be cryptic, I was very short on time.

If you know Avahi / mDNS then you know it is based on multicast, and stays within a subnet boundary (yes you can do things about that, but let's assume you didn't, and it operates within the multicast / broadcast domain as intended), this is why it always uses .local - it will not work with your internal domain, and neither should it.

So is pi-star ignoring your domain name, no, it will collect that from DNS and work with it perfectly well. Do you need to tell Pi-Star what your domain is, no it will pick it up from DHCP, and if you do not deliver it via DHCP, your router will usually have some method to make that not matter.

Your machine may not be configured for mDNS / Avahi / Bonjor, this would stop you being able to resolve .local addresses (depends on your OS, something Pi-Star has no idea about when you see the issue/motd), but it's in the issue / motd becuase Pi-Star does / can use it. If you were a mac user (mDNS is on by default) or you have mDNS on your machine for some other reason, it would be working.

I hope this makes sense, and if not, feel free to ask more questions, but I can tell you that it does work as intended.