Although my primary DNS is my Synology and the IP returned for ‘beatificabytes.be’ is expected to be the IP of my NAS, Chrome tried to access my blog on the web instead of locally. I thought it was an issue with the DNS and wanted to know how it resolved my domain name.
Click to Read More
Windows is caching the IP resolved by a DNS. So, thinking my DNS was possibly off when Chrome tried to resolve my domain name, I had to view the content of the cache. This can be done with the following command:
ipconfig /displaydns
The result was clear. My DNS didn’t answer itself and the domain name was therefore resolved by the DNS of my provider:
www.beatificabytes.be
—————————————-
Record Name . . . . . : www.beatificabytes.be
Record Type . . . . . : 5
Time To Live . . . . : 30
Data Length . . . . . : 8
Section . . . . . . . : Answer
CNAME Record . . . . : <myNAS>.diskstation.me
Record Name . . . . . : <myNAS>.diskstation.me
Record Type . . . . . : 1
Time To Live . . . . : 30
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 91.182.141.78
So, I tried to just flush the cache to see if my DNS would now resolve the domain name. The command to do so is:
ipconfig /flushdns
For information purpose, here are the commands to respectively turn off/on the DNS cache until next reboot:
net stop dnscache
net start dnscache
Flushing the DNS didn’t solve the issue unfortunately 🙁
Neither ipconfig /release nor ipconfig /renew did solve the issue either*… But this post is to keep a note about viewing/flushing the DNS cache only 😉
* To be continued…
Leave a Reply