Discussion:
Configuring a Bonjour host name
(too old to reply)
Jason Thorpe
2018-04-06 20:14:00 UTC
Permalink
I now have my RPI working perfectly happily in my network environment looking up the Bonjour names of the hosts it needs to care about using the mdns nsswitch module. However, it’s not obvious to me how to configure mdnsd to respond to queries for the RPI’s host name. The host name is configured as “nixie-dev”, and I’d like to be able to connect to the RPI using “nixie-dev.local”.

Am I just missing something (obvious or not), or is there not currently a way to do this?

Thx.

-- thorpej


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Jared McNeill
2018-04-07 10:20:16 UTC
Permalink
To advertise yourself on the network, put "mdnsd=YES" in rc.conf

For looking up other hosts from the RPI, set "hosts: files multicast_dns
dns" in nsswitch.conf

Cheers,
Jared
I now have my RPI working perfectly happily in my network environment looking up the Bonjour names of the hosts it needs to care about using the mdns nsswitch module. However, it’s not obvious to me how to configure mdnsd to respond to queries for the RPI’s host name. The host name is configured as “nixie-dev”, and I’d like to be able to connect to the RPI using “nixie-dev.local”.
Am I just missing something (obvious or not), or is there not currently a way to do this?
Thx.
-- thorpej
Jason Thorpe
2018-04-07 22:47:57 UTC
Permalink
Post by Jared McNeill
To advertise yourself on the network, put "mdnsd=YES" in rc.conf
For looking up other hosts from the RPI, set "hosts: files multicast_dns dns" in nsswitch.conf
Christos’s latest change made it a *little* better in that now it responds *at all*. However, now it seems to decide that “nixie-dev.local” is in use by something else and keeps switching to other names, such as “nixie-dev-59.local” and “nixie-dev-123.local”. This is somewhat unsatisfying :-)

—thorpej


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Jason Thorpe
2018-04-07 22:50:57 UTC
Permalink
Post by Jason Thorpe
Post by Jared McNeill
To advertise yourself on the network, put "mdnsd=YES" in rc.conf
For looking up other hosts from the RPI, set "hosts: files multicast_dns dns" in nsswitch.conf
Christos’s latest change made it a *little* better in that now it responds *at all*. However, now it seems to decide that “nixie-dev.local” is in use by something else and keeps switching to other names, such as “nixie-dev-59.local” and “nixie-dev-123.local”. This is somewhat unsatisfying :-)
Oops, forgot to paste the logs:

Apr 7 15:29:19 nixie-dev mDNSResponder: ResolveSimultaneousProbe: 6C952000 Our Record 3 lost: 00303520 4 nixie-dev.local. Addr 192.168.1.100
Apr 7 15:29:19 nixie-dev mDNSResponder: ResolveSimultaneousProbe: 6C952000 Pkt Record: FBD7E41B 16 nixie-dev.local. AAAA 2600:1700:BAB1:48F0:C8D2:0303:18D1:5136
Apr 7 15:29:19 nixie-dev mDNSResponder: ResolveSimultaneousProbe: 6C952000 Our Record 3 lost: 00303520 4 nixie-dev.local. Addr 192.168.1.100
Apr 7 15:29:19 nixie-dev mDNSResponder: ResolveSimultaneousProbe: 6C952000 Pkt Record: FBD7E41B 16 nixie-dev.local. AAAA 2600:1700:BAB1:48F0:C8D2:0303:18D1:5136
Apr 7 15:29:19 nixie-dev mDNSResponder: ResolveSimultaneousProbe: 6C952000 Our Record 3 lost: 00303520 4 nixie-dev.local. Addr 192.168.1.100
Apr 7 15:29:19 nixie-dev mDNSResponder: mDNSCoreReceiveResponse: Received from 192.168.1.100:5353 16 nixie-dev.local. AAAA FE80:0000:0000:0000:42A5:EFFF:FEDC:4E46
Apr 7 15:29:19 nixie-dev mDNSResponder: mDNSCoreReceiveResponse: ProbeCount 1; will deregister 16 nixie-dev.local. AAAA 2600:1700:BAB1:48F0:C8D2:0303:18D1:5136
Apr 7 15:29:19 nixie-dev mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 6C952B14 nixie-dev-2.local. (Addr) that's already in the list
Apr 7 15:29:19 nixie-dev mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 6C952E98 100.1.168.192.in-addr.arpa. (PTR) that's already in the list
Apr 7 15:29:19 nixie-dev mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 6C954B14 nixie-dev-2.local. (AAAA) that's already in the list
Apr 7 15:29:19 nixie-dev mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 6C954E98 6.4.E.4.C.D.E.F.F.F.F.E.5.A.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. (PTR) that's already in the list
Apr 7 15:29:19 nixie-dev mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 6C958E98 6.3.1.5.1.D.8.1.3.0.3.0.2.D.8.C.0.F.8.4.1.B.A.B.0.0.7.1.0.0.6.2.ip6.arpa. (PTR) that's already in the list
Apr 7 15:29:19 nixie-dev mDNSResponder: Local Hostname nixie-dev.local already in use; will try nixie-dev-2.local instead
Apr 7 15:29:20 nixie-dev mDNSResponder: ResolveSimultaneousProbe: 6C952000 Pkt Record: 00303520 4 nixie-dev-2.local. Addr 192.168.1.100
Apr 7 15:29:20 nixie-dev mDNSResponder: ResolveSimultaneousProbe: 6C952000 Our Record 2 won: FBD7E41B 16 nixie-dev-2.local. AAAA 2600:1700:BAB1:48F0:C8D2:0303:18D1:5136
Apr 7 15:29:20 nixie-dev mDNSResponder: ResolveSimultaneousProbe: 6C952000 Pkt Record: 00303520 4 nixie-dev-2.local. Addr 192.168.1.100
Apr 7 15:29:20 nixie-dev mDNSResponder: ResolveSimultaneousProbe: 6C952000 Our Record 2 won: FBD7E41B 16 nixie-dev-2.local. AAAA 2600:1700:BAB1:48F0:C8D2:0303:18D1:5136
Apr 7 15:29:20 nixie-dev mDNSResponder: ResolveSimultaneousProbe: 6C952000 Pkt Record: 00303520 4 nixie-dev-2.local. Addr 192.168.1.100
Apr 7 15:29:20 nixie-dev mDNSResponder: ResolveSimultaneousProbe: 6C952000 Our Record 1 won: FBD7E41B 16 nixie-dev-2.local. AAAA 2600:1700:BAB1:48F0:C8D2:0303:18D1:5136
Post by Jason Thorpe
—thorpej
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Christos Zoulas
2018-04-07 22:55:42 UTC
Permalink
Post by Jared McNeill
Post by Jared McNeill
To advertise yourself on the network, put "mdnsd=YES" in rc.conf
For looking up other hosts from the RPI, set "hosts: files
multicast_dns dns" in nsswitch.conf
Christos’s latest change made it a *little* better in that now it
responds *at all*. However, now it seems to decide that
“nixie-dev.local” is in use by something else and keeps switching to
other names, such as “nixie-dev-59.local” and
“nixie-dev-123.local”. This is somewhat unsatisfying :-)
does updating to the one from netbsd-8 work?

christos


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Jason Thorpe
2018-04-08 00:55:46 UTC
Permalink
Post by Christos Zoulas
does updating to the one from netbsd-8 work?
It logged this at startup:

mdnsd: CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements

…but seems to be behaving better, yes.

—thorpej


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Loading...