Tracking DNS route on a sub-dir?

Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy.
This forum is not for asking programming related questions.

Moderator: General Moderators

Post Reply
User avatar
Jenk
DevNet Master
Posts: 3587
Joined: Mon Sep 19, 2005 6:24 am
Location: London

Tracking DNS route on a sub-dir?

Post by Jenk »

Wasn't sure where to put this, sorry.

We've just rolled out a new website, on a new machine. However there is one querk.. one of the sub-directories seems to point to the old web-server, thus producing the old content and not the new content.
The root pages, and other sub-directories (which are all menu options) all work fine, and we have updated the main page to test if we have not mixed up the machines etc.

So, basically we have:

/htdocs (http://www.thesite.com/)
-/about (http://www.thesite.com/about)
-/contact (http://www.thesite.com/contact)
-/more (http://www.thesite.com/more)

If the user navigates to our site, then clicks on the "about" link they are shown the old content and not the new, yet when they click the other links they are seeing the new content. The about directory does exist and has correct permissions.

all the file permissions are 100% correct, double, triple and quadruple checked.. this really is turning into a head scratcher. My only idea at the moment is somehow the DNS routing is confusing between the new and old, our ISP assures us the records have been updated (which they have, as is apparent by viewing the new site) and it has been a month or two since the change so they should have propogated across the 'net by now.. but as Tim Allen would say.. arugh?! Is there a traceroute for DNS and sub-directories (not just machine names/ips)?

Any ideas anyone? :?

Apache/2.2.3 on SuSE 10.1 if that helps.

EDIT: access-logs backup what I thought about DNS, there are no entries for the "/about" link, but they do show the others. :?
timvw
DevNet Master
Posts: 4897
Joined: Mon Jan 19, 2004 11:11 pm
Location: Leuven, Belgium

Post by timvw »

DNS simply resolves 'hostname' to ip.. So in case there was a problem you wouldn't be able to surf to your site at all..

the fact that /x and /x/y are working differently more seems like an apache or webproxy problem...
User avatar
Jenk
DevNet Master
Posts: 3587
Joined: Mon Sep 19, 2005 6:24 am
Location: London

Post by Jenk »

Yeah, that's what I was sure of about DNS, but the apache logs show no attempt to access /about.

I'll see if I can poke someone about the proxy (if we have one)
timvw
DevNet Master
Posts: 4897
Joined: Mon Jan 19, 2004 11:11 pm
Location: Leuven, Belgium

Post by timvw »

I meant to say 'webcache' ;) (Although most proxies offer caching too these days)
User avatar
Jenk
DevNet Master
Posts: 3587
Joined: Mon Sep 19, 2005 6:24 am
Location: London

Post by Jenk »

webcache is clear (or rather, has been cleared.)

It appears there is a DNS record mishap, as I also noticed I had my local hosts file to point to the new server, so removed that entry and now the entire site points all over the place. Sometimes new, sometimes old.
Post Reply