Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Steve Pitts]

Folks,

I've had my DNS323 sending me automated email messages for many months now but a couple of weeks ago I 'upgraded' my Virgin Media broadband and part of that process was replacing the existing cable modem and D-Link DIR615 combination with a shiny new branded Super Hub (which acts as modem, router and gigabit hub) and ever since the emails from the NAS have not been appearing. Having found the time to do some investigation this weekend I discovered that the LAN settings on the NAS were showing the router IP address in the DNS1 field but apparently the Super Hub does not act as a DNS server or forward on the DNS requests.

Checking out the IP configurations on various PCs I see the Virgin DNS servers (194.168.4.100 and 194.168.8.100) listed and all of these systems are set up to 'obtain DNS server address automatically'. If I change the DNS1 and DNS2 values on the DNS323 LAN Settings page to the Virgin DNS addresses then I get dumped out of the web interface and upon logging back in DNS1 has reverted to the router IP address.

In that state (router IP as DNS1 and one of the Virgin Media servers as DNS2) the email process seems to be working again, but the time it takes to send a test email suggests that it is waiting for the attempt via DNS1 to fail before using DNS2. Is there any way that I can persuade the DNS323 to work the same way as the various PCs and pull the public DNS entries into DNS1 and DNS2 rather than using the router/gateway IP?? Obviously the ideal solution would be for the Super Hub to handle DNS forwarding, but I see complaints about this 'feature' dating back over a year so I don't hold out a lot of hope there.

[Steve Pitts]

Hmmm, and it appears that the problem gets worse because the next time the IP lease is renewed the DNS2 entry disappears and I stop receiving emails again. Since I've had no responses here and can find no way of getting the Virgin SuperHub to respond to DNS requests, it looks like I'm going to have to figure out how to correct this via ffp

[JoeNAS]

I've put the DNS-addresses from my provider in the DNS-323 - and it works. Maybe you could give this a try?

Jan

[dosborne]

Yes, you should be able to put the DNS addresses of your ISP into the DNS-323 NAS and/or use a public DNS server.

If you are having trouble configuring the values, use the reset button and/or return to factory defaults option, then reconfigure all your settings.

[Wiggs]

I also have used the DNS IPs provided by my ISP and it works fine.  Otherwise you can use public DNS servers.


Regards,


Wiggs

[Steve Pitts]

Thanks for the comments folks. Would I be right in guessing that those that have successfully set the DNS1 and DNS2 entries are using Static IP definitions in the DNS323?? All of my devices are set up for DHCP and the router is set to dish out fixed IP addresses based on MAC address. On that basis I would have preferred to leave the NAS set to DHCP Client but I've now set it to Static IP with the public DNS values that all other devices are setting for the DNS servers and (thus far) that appears to have worked.

[dosborne]

I used to have set IP addresses static in each device but I switched to a system similar to you to reserve lease addresses based on the MAC address as it gives central control and makes it easier to manage.