> On Mar 29, 2016, at 2:47 AM, Quinn The Eskimo! <[email protected]> wrote: > > > On 28 Mar 2016, at 02:48, Jeff Johnson <[email protected]> > wrote: > >> Is that supposed to happen? > > Yes. Think of the analogous case with IPv4: if you register a service in > "local.", you want the service registered with your standard IPv4 address.
Do you? I'm not clear on why you'd want local services resolved to internet routable IPv4 or IPv6 addresses. I thought the whole point of the local domain was to restrict it to link-local. I don't know whether I've seen the IPv4 case, because it's more difficult to get a global IPv4 address from behind a router than it is to get a global IPv6 address. >> And is there any way to stop it? > > Definitely not at the NSNetService layer. > > At the DNS-SD layer (<dns_sd.h>) you have a lot more flexibility. For > example, you could register your own A record (DNSServiceRegisterRecord) and > then register your service with that name as its host (the `host` parameter > to DNSServiceRegister). I've never tried this myself but I can't see why it > wouldn't work. Thanks. I'll take a look. It may be more trouble than it's worth, but it's good to know there are options. > Overall, however, I think you'd be better off nagging the folks with the > broken client to fix their connection code. Heh, well, that's a bit tricky, to say the least. _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to [email protected]
