Re: mDNSResponder name resolution broken in 7.99.4

[Richard PALO <richard%netbsd.org@localhost>]

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

I tried:
> # /usr/sbin/mdnsd -debug
> CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements

in another session:
> nb32$ grep 5350 /etc/services 
> #                  5350        tcp    Reserved
> pcp-multicast      5350/udp    # Port Control Protocol        [IESG]                                                [IETF_Chair]                                                                        [RFC6887]
> nb32$ ping omnis.local
> ping: Cannot resolve "omnis.local" (Resolver internal error)


where it works okay on a different (linux) client:
> richard@odroid-001e06336dd6:/home/richard$ ping omnis.local
> PING omnis.local (192.168.0.6) 56(84) bytes of data.
> 64 bytes from omnis.local (192.168.0.6): icmp_seq=1 ttl=255 time=0.569 ms
> 64 bytes from omnis.local (192.168.0.6): icmp_seq=2 ttl=255 time=0.659 ms
>...



-- 
Richard PALO