Latest firmware has stopped local DNS connections

martinr said:

You said it used to work locally, so, the one thing you can try, which I'm sure you're trying to avoid, is a restore to factory default. It's a bit like doing a fresh install of Windows: once you've bitten the bullet and set aside the time, it's a very satisfying process - time-consuming rather than difficult. Go for it.

Click to expand...

Like you say, I really want to avoid doing that, as I've a number of settings which will take a lot of time to go through again. VPN, IP reservations, port forwards, DHCP... the list goes on.

I hoping there's a fix without having to do that...

I strongly suggest you take a backup using John's utility straight away: http://www.snbforums.com/threads/user-nvram-save-restore-utility-r19.19521/ After that, if you have to do a factory reset you can use it again to do a semi-clean restoration of your settings.

WannabeMKII said:

What can I do next, as this is a bit of a show stopper now as nothing can connect into my network via DDNS name

Click to expand...

What happens if you try to use the IP address rather than the DDNS name?

ColinTaylor said:

I strongly suggest you take a backup using John's utility straight away: http://www.snbforums.com/threads/user-nvram-save-restore-utility-r19.19521/ After that, if you have to do a factory reset you can use it again to do a semi-clean restoration of your settings.

Click to expand...

I'll check that out and make a backup.

ColinTaylor said:

What happens if you try to use the IP address rather than the DDNS name?

Click to expand...

Ah ha, now that's interesting, in that it won't connect even with the WAN IP, which has made me think...

Argh, it's dropped all the port forwarding I've now had to try to remember all the forwarded ports and also re-register the DDNS details.

So it appears the problem was with the port forwarding being wiped during the upgrade. Hmmm...

Thanks for the help troubleshooting!!!

No problem. I hope you get it going again.