Name Resolution

[Guest]

We have DNS services running on a UNIX ( SUN solaris). We also have active
directory (win2k SP4) IN MIXED MODE. The domain name is xyz.abc.org. We have
problem resolving FQDN. If we use the absolute IP, it is OK. If we use the
short name ( like suppapp:<port>/index.htm) we get to the desired screen. But
if we use
suppapp.xyz.abc.org:<port>/index.htm, it failes to resolve and we get either
page can't be displayed or just the white screen. The DHCP is also a SUN box
and client PCs are configured for DHCP. On clients we have tried the DNS
suffix as abc.org and xyz.abc.org both. The results are same above
Any suggestions.
Rajeev

 

[ptwilliams]

Two points:

1. When you use periods (or dots, or full-stops) '.' in IE the request is
deemed an external address and is passed to the proxy server. You'll need
to configure an exception if this is indeed an internal address (bypass for
local doesn't work), e.g. *.xyz.com.

2. I don't think you should be stipulating the /index.htm - firstly, that
shouldn't follow the port (I believe) and secondly, the job of the web
server is to stick that on the end. Try suppapp.xyz.com:<port> instead.


3. Is this really AD related?? You'd probably have more joy in an IE or
Win general forum... ;-)


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


We have DNS services running on a UNIX ( SUN solaris). We also have active
directory (win2k SP4) IN MIXED MODE. The domain name is xyz.abc.org. We have
problem resolving FQDN. If we use the absolute IP, it is OK. If we use the
short name ( like suppapp:<port>/index.htm) we get to the desired screen.
But
if we use
suppapp.xyz.abc.org:<port>/index.htm, it failes to resolve and we get either
page can't be displayed or just the white screen. The DHCP is also a SUN box
and client PCs are configured for DHCP. On clients we have tried the DNS
suffix as abc.org and xyz.abc.org both. The results are same above
Any suggestions.
Rajeev