Nitebirdz responded: >I'm not sure, but I have a feeling he was actually referring to a change >in the DNS records. In other words, this HTML-based redirection will only >work if both www.foo.com and simply foo.com resolve to the proper IP >address. > >As far as I remember, you set it up by modifying the A records on your >DNS server. Check out the docs on DNS configuration from >http://www.linuxdoc.org and that should do it. Bingo. When I first saw the post I figured that he had two separate machines running, one at foo.com and another at www.foo.com. The redirection scheme will only work if foo.com has httpd running. Even if it did, one would have to place redirection files in each of the directories that users might have bookmarked. So, if there are indeed two machine, turn off httpd on the foo.com machine and let the user get an error. That is done at lots of places. Take sendmail.org. If you try that machine, it will fail. One has to use www.sendmail.org. I suggest the same for this situation. Do not run httpd on foo.com. If there are two machines, there should already be separate DNS entries for foo.com, www.foo.com and maybe even ftp.foo.com. But, if foo.com and www.foo.com are the one and same machine, redirection is not required. I guess we need for information about the layout of these machines so that we can provide the best answer for the situation. MB -- e-mail: [EMAIL PROTECTED] Bart: Hey, why is it destroying other toys? Lisa: They must have programmed it to eliminate the competition. Bart: You mean like Microsoft? Lisa: Exactly. [The Simpsons - 12/18/99] Visit - URL:http://www.vidiot.com/ (Your link to Star Trek and UPN) _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
