Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: dns service error: name conflict

See original GitHub issue

I’m running homebridge on raspberry pi 3 B

How do I fix this?

`/usr/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:56 dns_sd.DNSServiceRegister(self.serviceRef, flags, ifaceIdx, name, ^

Error: dns service error: name conflict at Error (native) at new Advertisement (/usr/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:56:10) at Object.create [as createAdvertisement] (/usr/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:64:10) at Advertiser.startAdvertising (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Advertiser.js:43:30) at Bridge.Accessory._onListening (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:526:20) at emitOne (events.js:96:13) at HAPServer.emit (events.js:188:7) at HAPServer._onListening (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:185:8) at emitOne (events.js:96:13) at EventedHTTPServer.emit (events.js:188:7)`

Any ideas?

Issue Analytics

State:
Created 7 years ago
Comments:19 (1 by maintainers)

Top GitHub Comments

2reactions

KhaosTcommented, Nov 7, 2016

Give the accessory a different name

Sent from my iPhone

On Nov 7, 2016, at 6:33 AM, mehak-bhatia notifications@github.com wrote:

I’m running homebridge on raspberry pi 3 B

How do I fix this?

`/usr/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:56 dns_sd.DNSServiceRegister(self.serviceRef, flags, ifaceIdx, name, ^

Error: dns service error: name conflict at Error (native) at new Advertisement (/usr/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:56:10) at Object.create as createAdvertisement at Advertiser.startAdvertising (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Advertiser.js:43:30) at Bridge.Accessory._onListening (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:526:20) at emitOne (events.js:96:13) at HAPServer.emit (events.js:188:7) at HAPServer._onListening (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:185:8) at emitOne (events.js:96:13) at EventedHTTPServer.emit (events.js:188:7)`

Any ideas?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

0reactions

darrylhodginscommented, Apr 7, 2018

For anyone else coming across this issue, this:

Give the accessory a different name

…appears to mean that the hostname of the Pi needs to be different from the name of the bridge in the configuration. For example, this will fail:

$ hostname
raspberry-pi-homebridge

config.json:

{
	"bridge": {
		"name": "Raspberry Pi Homebridge",
		...
	},
	...
}

Change either the hostname or the bridge.name to make it work 😃

Top Results From Across the Web

dns service error: name conflict · Issue #903 - GitHub

I'm running homebridge on raspberry pi 3 B. How do I fix this? `/usr/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:56

Fix conflicting records errors - Google Domains Help

To fix conflicting record errors, try the following: Turn off browser extensions like password managers or grammar checkers. In the "DNS" tab, confirm...

Common DNS Server Errors And How To Fix Them - TinyDNS

Solution: Narrow down your DNS error to a specific issue. For example, if you are having mail delivery issues, you should first check...

Fix conflicting DNS domain errors for interface VPC endpoints

Short description. The following are common reasons for receiving a conflicting DNS domain error when creating an interface VPC endpoint: You ...

Why Is a Message Indicating Conflict with an Existing Record ...

For example, CNAME resolution has been added to the local DNS and cached. When the client adds MX resolution (using the mailbox to...