Sunday, July 26, 2009

DNS issues resolved (sort of)

This is going to be a boring post if you are looking for pictures of Georgie. But I'm hoping someone out there knows more about DNS settings than I do. If you know anything about DNS settings, you know more than I do.

For almost 2 years, it's troubled me that when our URL is entered without a third level domain (i.e. seiferthobbins.com instead of www.s-h.com) it redirects you to a no-longer-existent 3rd level domain - wedding.seiferthobbins.com. I created that sub-domain back when we were getting married and started a registry online. I long ago deleted it.

The problem is I have never been able to find where the re-direct setting is again to change it back.

Now I doubt very many people are clamoring to seiferthobbins.com and being thwarted in their attempts to find us, but it bothers me nonetheless.

Our site is a simple Blogger blog, but, just to keep it interesting, we bought our own domain 2 or 3 years ago. I bought it when Google Apps came out and use that service for the site. That way Nikki and I have our own email at that domain and nice features like shared docs and calendars.

The domain is actually registered through enom, who has one of the crappier interfaces for managing a domain. Actually it looks like "real" customers have a nice interface, but Google Apps customers have a very barebones, useless interface.

So the problem is that I can't find where the URL pointing is even happening. Neither the Google Apps dashboard nor the enom interface have any indication of it.

Every few months I try in vain to find the lost tab where I set this up. Today though I actually thought of a workaround -- a URL redirect from wedding back to www. This is totally stupid but it works. If you go to seiferthobbins.com and look quickly at the address bar, you'll see that you are being first redirected to wedding.seiferthobbins.com, then to www.seiferthobbins.com.

Thankfully no one is paying me to administer this blog, or I'd probably be replaced.

Anyway, if you've ever been in this situation and you're reading this, please let me know how to fix it for real.

p.s. Again I make no claims at knowing anything about DNS, so if my nomenclature is inaccurate, please forgive me.

No comments: