Jump to content
Compatible Support Forums
Sign in to follow this  
BladeRunner

DNS possibly, long, seeking ideas!!

Recommended Posts

Hello all,

Come accross a really annoying problem.

It's quite long, but if anybody has any ideas I'd be glad to hear them.

OK, local Intranet server.

I'll give the proper names here as they aren't accessable to the outside world.

Recently changed the Intranet 'Home Page'.

Intranet is running on a server called glycine.ourdomain.com

This is a LINUX box.

We have 3 DNS servers, a Win2k Primary, a Win2k Secondary and a LINUX Secondary.

We created an alias 'web.ourdomain.com' pointing towards glycine.ourdomain.com

All 3 of our DNS servers are showing this entry.

If I open up an IE window and simply type 'web' it goes off and correctly displays our Intranet pages.

However, if we type web.ourdomain.com it displays our old Intranet pages.

I have 1 machine running Whistler beta 2 which of course is running IE6.

This machine goes to the correct page if I type 'web' or 'web.ourdomain.com'

All the other machines are running IE5 or IE5.5 and they don't.

I have tried clearing the IE cache and history, still same problem.

 

I know this question is very open, I think there are so many possible variations on setup etc.

Just wondering if anybody has ever experienced similar and/or have some things I could try?

 

Ta

Share this post


Link to post

Normally, when I see issues of improper page loading when both sites are on the same machine, I usually check the host header names for each site first. Does your Linux box support this?

Share this post


Link to post

Found the problem!! :-)

Bit of a mess-up.

Intranet used to run on a machine called gate.ourdomain.com

web.ourdomain.com was an alias for this machine.

I made the DNS change so that web.ourdomain.com was now an alias for glycine.ourdomain.com

All our users proxy through gate.ourdomain.com and somewhere in it's configuration file was basically the line 'I am web.ourdomain.com'

All our users were hitting the proxy server, it didn't bother checking the DNS because as far as it was concerned it was the target machine!

So, we remove that line and suddenly everything bursts into life! :-)

Share this post


Link to post

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×