D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: dmfabri on September 04, 2014, 08:20:17 AM

Title: Unable to find DNS record for time server ntp1.dlink.com
Post by: dmfabri on September 04, 2014, 08:20:17 AM
Overnight, I found that I could not connect wireless to the internet thru dir-655.  The message in the logs is: Unable to find DNS record for time server ntp1.dlink.com".  LAN connections work fine.  I've rebooted router, factory reset, reloaded a backup config, set time/date manually -  all to no avail. Any ideas out there? ???
Title: Re: Unable to find DNS record for time server ntp1.dlink.com
Post by: FurryNutz on September 04, 2014, 08:29:02 AM
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)



Internet Service Provider and Modem Configurations


Wireless Configurations
Links>Wireless Installation Considerations (http://forums.dlink.com/index.php?topic=48327.0) and Managing Signal Congestion (http://forums.dlink.com/index.php?topic=53228.0) and Good Neighbour Policy (http://forums.dlink.com/index.php?topic=10634.0)


Router Placement
Forum User - "Well I feel really dumb. After moving the router away from other electronic devices my speeds are back to normal. Just a heads up for anyone experiencing slow speeds, you might want to move it away from other electronics and see if that helps."
3-6' feet minimum safe distance between devices.
Placement on main level floor and central in the building and WELL ventilated is preferred. Not in basements or closets as building materials, or near by electronics devices could interfere or hinder good signal propagation.
Title: Re: Unable to find DNS record for time server ntp1.dlink.com
Post by: FurryNutz on September 15, 2014, 10:08:36 AM
Any status on this?  ???

Overnight, I found that I could not connect wireless to the internet thru dir-655.  The message in the logs is: Unable to find DNS record for time server ntp1.dlink.com".  LAN connections work fine.  I've rebooted router, factory reset, reloaded a backup config, set time/date manually -  all to no avail. Any ideas out there? ???