I have just applied the latest service pack for DSM 5.0. Soon after, I started to experience connection issues to my own blog from my Intranet. This was due to some (???) issues with the DNS Service running on my Synology.
Click to Read More
Issue confirmed: executing a “ping beatificabytes.be” in a CMD prompt was returning the internet IP of my ADSL Modem, instead of the IP of my NAS.
As a reminder: I did configure my Router and my Synology’s DNS Service to be able to access my blog on my intranet with it’s actual FQDN (See here). And after the upgrade from DSM 4.0 to DSM 5.0, I had to enable the “Resolution Service” in the “DNS Server”.
Now, to solve the connection issue experienced after updating DSM 5.0:
- On the Synology, in the “DNS Server” configuration pane, I had first to:
- Disable the “Resolution Service” and clicked Apply
- Re-enable the “Resolution Service” and clicked Apply
- Next, on my PC, in a CMD prompt, I did executed:
- ipconfig /flushdns
- ipconfig /renew *
- ping beatificabytes.be
Et voilà !
Leave a Reply