Connect

 

The Standard Disclaimer

The views expressed on this blog and its related web sites or podcasts are mine alone and do not reflect the views of my employer, clients, investors, wife, children, pets, parents, friends, friends-of-friends or anyone else with whom I may be acquainted.

 

Navigation
« Advertising: What's Next? | Main | Media Temple Grid Server Update: Too Little, Too Late »
Tuesday
Dec052006

Dueling DNS or "Why I Should Have NEVER Used Media Temple"

OK - now I'm getting really pissed. I changed the DNS for brandbrains.net last night before I went to bed. When I arrived at the office today, it appeared as though DNS had propagated.

However, as I'm sitting here (quite literally), Media Temple pushes an update to DNS which then switched DNS BACK to their name servers and subsequently, to my old Wordpress install. I'm not really sure how this is possible, given that I instructed the registrar (GoDaddy) to change the DNS authority for the domain but lo and behold, there it is. So, the posts that I made earlier today ended up in the wrong instance of wordpress.

When is this nightmare going to end?

UPDATE: Looks like things are starting to right themselves, but there are still some DNS caching issues. Some people might still be seeing the old Wordpress instance. Hopefully it will clear up in the next 24 hours.

NOTE: In all fairness, these issues no longer have anything to do with Media Temple - caching is just a function of how some DNS servers work.

[tags]Media Temple, Web Hosting, Customer Support, John Federico, On Digital Media, Podcasting, Blogs, Blogging[/tags]

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>