Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: mDNSResponder name resolution broken in 7.99.4
> On 6 Sep 2016, at 18:14, Richard PALO <richard%netbsd.org@localhost> wrote:
>
> Le 24/02/15 08:19, Fredrik Pettai a écrit :
>> Hi,
>>
>> I noted that mDNSResponder name resolution stopped working on 7.99.4 (built 4 feb)
>>
>> -bash-4.3$ more /etc/nsswitch.conf | grep hosts
>> hosts: files dns mdnsd multicast_dns
>> # hosts: dns, files, nis, mdnsd, multicast_dns
>>
>> -bash-4.3$ ping morran.local
>> ping: Cannot resolve "morran.local" (Resolver internal error)
>>
>> A datapoint is that 7.99.3 worked fine.
>> (and 7_BETA (as of 201502191150Z) still works as expected...)
>>
>> -bash-4.3$ ping frpet1n.local
>> PING frpet1n.local (192.168.1.103): 64 data bytes
>> 64 bytes from 192.168.1.103: icmp_seq=0 ttl=255 time=1.417000 ms
>> ^C
>>
>> /P
>>
>
> I came across this same issue... NetBSD 7.99.36 i386
That was fixed a long time ago AFAICR...
At least it works for me with fairly recent (amd64) kernel...
bash-4.3# uname -a
NetBSD stinky 7.99.36 NetBSD 7.99.36 (GENERIC.201608250400Z) amd64
bash-4.3# ping morran.local
PING morran.local (193.10.5.78): 56 data bytes
64 bytes from 193.10.5.78: icmp_seq=0 ttl=255 time=0.098882 ms
^C
----morran.local PING Statistics----
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.098882/0.098882/0.098882/0.000000 ms
/P
Home |
Main Index |
Thread Index |
Old Index