Devin Hughes

Yes, I hit the 5 tries per hour limit on the production servers. The problem I ran into is that the documentation was a little confusing for me since the...

I did notice that when I was watching the queries being resolved. I think the issue for me was more to do with not knowing what I should put specifically...

@Yannik Oh, and what I meant about the DNS record at dnsmadeeasy is the NS record is not allowed to have `auth.example.com` as the subdomain *and* the NS record destination....

@Yannik No reason other than it was in place already. The change was simple in the config for the NS restriction - the server just got called ns0.auth.example.com. instead of...

"(Every Machinekit machinetalk service is announced by two PTR records" The issue is that older underscore style record isn't being published from the latest build on the hardware I'm using...

"Or you mean that the Domain name used to be something like _launchercmd._sub._machinekit._tcp.local" Yes, exactly. Previously, the SRV and TXT records were enumerable using the domain name `_launchercmd._sub._machinekit._tcp.local`. What happened...

Multi-machinekit instances in a physically isolated private network has been my use case since 2016. I'm not sure if @machinekoder and @mhaberler had that case in mind, but we do...

I totally agree with making the naming more consistent. It took me a little while to figure out that the service names were being published by the python `service` file...

I think it should be either the hostname or the GUID. Plus, verbosely including ``` Machinetalk Service ``` in light of the character limit sounds like a misstep. Looking back...

Yes, that's what I'm doing here. I extended machinekit.ini template with: ``` # DNS records announcing services are normalized for clarity, and to avoid # accidental collisions in the local...