Re: Is there something broken with DNS on Yosemite (and earlier OS versions) when running a daemon?
Re: Is there something broken with DNS on Yosemite (and earlier OS versions) when running a daemon?
- Subject: Re: Is there something broken with DNS on Yosemite (and earlier OS versions) when running a daemon?
- From: Stéphane Sudre <email@hidden>
- Date: Wed, 18 Feb 2015 11:12:10 +0000
- Thread-topic: Is there something broken with DNS on Yosemite (and earlier OS versions) when running a daemon?
On 9 févr. 2015, at 15:52, Stéphane Sudre wrote:
>
> On 9 janv. 2015, at 16:54, Stéphane Sudre wrote:
>
>> On 8 janv. 2015, at 01:22, Dieter Siegmund wrote:
>>
>>> Hi Stéphane,
>>>
>>> Have you filed a bug report for this issue yet? That would be the best way forward to try to understand and hopefully resolve the problem you're running into.
>>
>> Problem ID #19426092 on Radar. (Source code, binary, installation package included).
>>
>> Either I'm doing something totally stupid or there's a bug.
>
> The problem still exists in OS X 10.10.2 GM (and would there be a newer seed of OS X, it would exist too).
>
> Trying to reset the udns and mdns caches via discoveryutil does not solve the issue.
>
> Is there a way to inform getaddrinfo it is a stubborn bozo and to require it to try to resolve hostnames as if it were the first request since the process was launched?
>
> I was thinking of trying to re-resolve the hostnames when SystemConfiguration notifies about DNS configuration changes but this would not help since the hostnames are already being re-resolved periodically with no effect.
The problem also exists if you use the CFHost APIs.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden