DNS Resolution Issue with Website?

Steve Sandau ssandau at gwi.net
Mon Nov 1 23:48:22 UTC 2004

>>>Don't know if this is the place to post this, but we'll give it a shot.
>>>Got something happening that I can't quite figure out.  We are working with
>>>a company that has two domains.  The domains are www.checktech.us and
>>>www.checktech.us is registered with GoDaddy and is forwarded to
>>>www.checktechfinancial.com, which is registered with Network Solutions.
>>>A couple of weird things are happening.  First, when hovering over a link at
>>>www.checktechfinancial.com, rather than seeing the URL we are seeing the IP
>>>address of the web server.  Second, and probably caused by the same problem,
>>>there is a search function on www.checktechfinancial.com when is run through
>>>a third party search service.  The banners and such from
>>>www.checktechfinancial.com are supposed to show up on the search site, but
>>>don't unless the path to those images are change from a URL to the IP
>>>address of the web server hosting www.checktechfinancial.com.
>>>The other really weird thing is that the site seems to be using frames, even
>>>though there is absolutely nothing in the coding for frames.  If we move the
>>>entire site to a subfolder under our own site on our webserver, everything
>>>works correctly, even though we have to access it using
>>>www.ourdomain/checktechfinancial.com, with the exception of the search
>>>feature of course.
>>>I think something is wacked out in DNS, although I may be wrong.  If it is
>>>DNS, where could the problem be?

These are mostly (all?) webserver problems. Html code in the page you 
mention has "relative" links not fully-qualified ones. Links like 
"aboutus.html" are turned into complete links by the web server which 
adds its own identity to the front of the link. If it only knows itself 
by an IP number or you access the main page with an IP address, it'll 
use that. This probably accounts for all the problems you mention. with 
the  exception of the appearance of forms which I cannot explain.

The only way this is possibley a DNS problem that I can see is if your 
WWW server cannot properly do a reverse lookup on its own IP.

It is hard to tell thought without knowing what www software, what 
operating system, what flavor of DNS and so on. Further, most of those 
topics do not belong on this list anyway...

Steve Sandau

More information about the bind-users mailing list