Join the DZone community and get the full member experience.
Join For FreeDiscover the easy-to-use control panel and API that let you spend more time coding and less time managing your infrastructure. Brought to you in partnership with DigitalOcean
Everything in getting my personal site setup went fairly smoothly, including updating my registrar’s DNS records to point my domain name at my hosting provider. Being an impatient sort, I didn’t want to have to wait for the TTL on my domain name to expire, so I ran a dig request to see if my registrar had pushed through the change:
shell$ dig grepalex.com ;; ANSWER SECTION: grepalex.com. 3600 IN A 66.216.100.140
Indeed they had! Next up was trying to hit my website from my browser. When I did that however, Chrome was showing the my registrar’s advertising content. A few pokes around led me to Chrome’s web page which lets you invalidate its DNS cache:
chrome://net-internals/#dns
However even after invalidating Chrome’s cache it still showed the content from the registrar. The cool thing about Chrome’s internal page is that it actually shows you the cached IP address, which indeed was still the old value. Clearly the OSX DNS client was performing some additional caching. After some more digging around I found the (Mountain) Lion-specific command which did indeed successfully clean OSX’s cache:
shell$ sudo killall -HUP mDNSResponder
Hurray!
Learn about the optimized the configuration process to save your team time when running and scaling distributed applications, AI & machine learning workloads, hosted services, client websites, or CI/CD environments. Brought to you in partnership with DigitalOcean
Like This Article? Read More From DZone
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}