how-to block ads
|
billycar
join:2006-09-29
Lynchburg, VA
| [connectivity] Westell 327W has Duplicate Domain Name Servers
Under both of my LAN ethernet connected Apple computers, one running Tiger 10.4.11, the other Leopard 10.5.5, I get a warning message that I have duplicate Domain Name Servers. Here is an Apple System Profiler showing duplicate servers:
DNS:
Domain Name: myhome.westell.com
Server Addresses: 192.168.1.1, 192.168.1.1
DHCP Server Responses:
Domain Name: myhome.westell.com
Domain Name Servers: 192.168.1.1,192.168.1.1
Lease Duration (seconds): 0
DHCP Message Type: 0x05
Routers: 192.168.1.1
Server Identifier: 192.168.1.1
Subnet Mask: 255.255.255.0
This is off a Westell 327W.
The following log entry is under the Tiger system (similar one occurs under Leopard):
Dec 7 23:38:13 Acoustic-Piano-Mac mDNSResponder: Repeated transitions for interface en0 (192.168.1.40); delaying packets by 5 seconds
Dec 7 23:38:36 Acoustic-Piano-Mac mDNSResponder: NOTE: Wide-Area Service Discovery disabled to avoid crashing defective DNS relay 192.168.1.1.
Dec 7 23:48:24 Acoustic-Piano-Mac launchd: Server 481b in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[292]: exited abnormally: Hangup
Dec 7 23:48:24 Acoustic-Piano-Mac configd[61]: posting notification com.apple.system.config.network_change
Can I rid myself of this issue? Under 192.168.1.1 > Advanced > LAN > DNS, there was listed a second Host Name with the same 192.168.1.1 as the IP Address, but I deleted that to see if that would remove the duplicate listing above. It did not. I've tried resetting PRAM on both Macs.
I have moved from using one Wireless / one hardwired to all hardwired connections. Also I admit I experimented installing drivers for another wireless device, to see if it would run my Airlink101 3026 USB 2 more reliably under 10.5.5, but it did not. I removed that driver from the affected computer, eventually by re-installing the OS X altogether ("Nuke & Pave" technique).
The machine that had its OS X (Leopard) completely reinstalled, was done with no Migration. It was having kernel panics and other issues, perhaps complicated by the duplicate server.
How do I remove the Duplicate Server?
Any suggestions?
Need more information? | |
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
 ·Verizon Online DSL
 ·Skype
| Re: [connectivity] Westell 327W has Duplicate Domain Name Server
said by billycar  :How do I remove the Duplicate Server? You don't. The error message is simply saying that mDNS won't extend beyond the local LAN because your LAN uses DNS Relay that it detects as incompatible. It's an announcement that Wide-Area support was being prevented. That won't cause crashes, that will prevent them. Back in 2005, mDNS would crash routers. I haven't looked into the issue well enough to agree or disagree with this as a "bug." Regardless of that, mDNS is great for sharing folders and music around the office, most people don't want to on the WAN, so the DNS Relay issue is of little consequence.
The apparent duplication has nothing to do with it. You would get the same mDNS error if it was listed just once, the error message is talking about a capability problem with the DNS Relay itself, having nothing to do with it being listed twice. DNS returns are generally cached, so even if these queries did cascade, the cached answer or a retry would be used by the second entry.
I immediately bridged my 327W so I can't tell you how to avoid DNS Relay, should you want to. I personally don't like DNS Relay -- I don't quite know what problem they are solving with DNS Relay, but this duplication or mDNS message is not a reason to stop using it. The message is non-fatal and, to most, involves a feature they don't use. You can read more about mDNS or Bonjour/Zeroconf/Avahi in the various FAQs and decide whether to try to fix or work around it or leave it as it is.
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon
More features, more fun, Join BroadbandReports.com, it's free...
| |
-
|
