Re: Redirection of HTTP request
Gene Grimm wrote: We are a small local ISP with a mixture of Linux servers and an NT server. Most of our client web pages are currently hosted on the NT box. All of our email is hosted by our main Linux box. How should an HTTP request to site labeled domain.com be properly redirected to www.domain.com. -- http://www.networksonline.com/service.htm ICQ #58278887 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] in your dns, with a line like : www IN CNAME domain.com -- Youri Albinovanus System Administrator Tiscali Belgium 29-31 Ch. d'Ixelles 1050 BRUXELLES BELGIUM Tel. : +32 2 4000888 Fax. : +32 2 4000899 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Redirection of HTTP request
On Thu, 17 Aug 2000, Youri Albinovanus wrote: www IN CNAME domain.com and right after you'll find yourself running around head over heels ps. note the absence of the trailing dot... -- [-] ``And there are plenty of other innovative pieces of software such as Napster and ICQ.'' -- comment on ``Systems Software Research is Irrelevant'' at http://freshmeat.net/news/2000/08/05/965534399.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Redirection of HTTP request
Your domain 'domain.com' has some dns-entry pointing to your http-server (possibly apache). The A-record for www.domain.com should refer to the same IP as domain.com. The rest is the configuration of your webserver, where you possibly have to specify www.domain.com as an alias for domain.com. We are a small local ISP with a mixture of Linux servers and an NT server. Most of our client web pages are currently hosted on the NT box. All of our email is hosted by our main Linux box. How should an HTTP request to site labeled domain.com be properly redirected to www.domain.com. The NT-based DNS A-record for host 'www' under 'domain.com' points to an IP address allocated to IIS on the Windows NT machine. The DNS A-record for 'domain.com' points to the IP address allocated to our email server. These are two separate machines. Nearly ALL web sites are hosted on NT. ALL email is processed by our main Linux box. As a side note, I was assigned the sysadmin role after the fact. Summary: domain.com A -- mail server IP domain.com NS -- dns1.primedomain.com domain.com SOA -- dns1.primedomain.com, admin.primedomain.com wwwA -- NT server IP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Redirection of HTTP request
[...] GG Summary: domain.com A -- mail server IP GG domain.com NS -- dns1.primedomain.com GG domain.com SOA -- dns1.primedomain.com,admin.primedomain.com GG www A -- NT server IP This is what I would do with reasons: domain.com A -- web server IP because people will type domain.com. Netscape will try www.domain.com if nothing is listening at www.domain.com, IE won't AFAIK. What seems more elegant, domain.com CNAME -- name of the virtual hosting server, will not work because you cannot CNAME domain.com if you define other RRs under domain.com. www.domain.com CNAME -- domain.com so www works! domain.com SOA -- dns1.primedomain.com,admin.primedomain.com domain.com NS -- dns1.primedomain.com OK. You need another NS preferably on a different T. This is not some paperwork requirement, you want the domain name to resolve even if there is an outage. domain.com 10 MX -- mail server name domain.com 20 MX -- back-up mail server name Always try to accept mail even if the main server goes down (you don't know when the other daemons in the net will bounce queued mail, but you can adjust this on your back-up if there's an outage). On terminology: 'redirection' is not a good term to use in this case. In the context of http, it has a different meaning that does not concern DNS. EG: An http redirect tells a browser that hit www.domain1.com to go to www.domain2.com _at the HTTP level_. This is useful because it enables you to redirect, say, http://company.net/ to http://www.company.com/ and cause the location shown in the browser and remembered in bookmarks to change to http://www.company.com/. hope this helps, BM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Redirection of HTTP request
We are a small local ISP with a mixture of Linux servers and an NT server. Most of our client web pages are currently hosted on the NT box. All of our email is hosted by our main Linux box. How should an HTTP request to site labeled domain.com be properly redirected to www.domain.com. -- http://www.networksonline.com/service.htm ICQ #58278887
Re: Redirection of HTTP request
Gene Grimm wrote: We are a small local ISP with a mixture of Linux servers and an NT server. Most of our client web pages are currently hosted on the NT box. All of our email is hosted by our main Linux box. How should an HTTP request to site labeled domain.com be properly redirected to www.domain.com. -- http://www.networksonline.com/service.htm ICQ #58278887 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] in your dns, with a line like : www IN CNAME domain.com -- Youri Albinovanus System Administrator Tiscali Belgium 29-31 Ch. d'Ixelles 1050 BRUXELLES BELGIUM Tel. : +32 2 4000888 Fax. : +32 2 4000899
Re: Redirection of HTTP request
On Thu, 17 Aug 2000, Youri Albinovanus wrote: www IN CNAME domain.com and right after you'll find yourself running around head over heels ps. note the absence of the trailing dot... -- [-] ``And there are plenty of other innovative pieces of software such as Napster and ICQ.'' -- comment on ``Systems Software Research is Irrelevant'' at http://freshmeat.net/news/2000/08/05/965534399.html
Re: Redirection of HTTP request
Your domain 'domain.com' has some dns-entry pointing to your http-server (possibly apache). The A-record for www.domain.com should refer to the same IP as domain.com. The rest is the configuration of your webserver, where you possibly have to specify www.domain.com as an alias for domain.com. We are a small local ISP with a mixture of Linux servers and an NT server. Most of our client web pages are currently hosted on the NT box. All of our email is hosted by our main Linux box. How should an HTTP request to site labeled domain.com be properly redirected to www.domain.com. The NT-based DNS A-record for host 'www' under 'domain.com' points to an IP address allocated to IIS on the Windows NT machine. The DNS A-record for 'domain.com' points to the IP address allocated to our email server. These are two separate machines. Nearly ALL web sites are hosted on NT. ALL email is processed by our main Linux box. As a side note, I was assigned the sysadmin role after the fact. Summary: domain.com A -- mail server IP domain.com NS -- dns1.primedomain.com domain.com SOA -- dns1.primedomain.com, admin.primedomain.com wwwA -- NT server IP
Re: Redirection of HTTP request
[...] GG Summary: domain.com A -- mail server IP GG domain.com NS -- dns1.primedomain.com GG domain.com SOA -- dns1.primedomain.com,admin.primedomain.com GG www A -- NT server IP This is what I would do with reasons: domain.com A -- web server IP because people will type domain.com. Netscape will try www.domain.com if nothing is listening at www.domain.com, IE won't AFAIK. What seems more elegant, domain.com CNAME -- name of the virtual hosting server, will not work because you cannot CNAME domain.com if you define other RRs under domain.com. www.domain.com CNAME -- domain.com so www works! domain.com SOA -- dns1.primedomain.com,admin.primedomain.com domain.com NS -- dns1.primedomain.com OK. You need another NS preferably on a different T. This is not some paperwork requirement, you want the domain name to resolve even if there is an outage. domain.com 10 MX -- mail server name domain.com 20 MX -- back-up mail server name Always try to accept mail even if the main server goes down (you don't know when the other daemons in the net will bounce queued mail, but you can adjust this on your back-up if there's an outage). On terminology: 'redirection' is not a good term to use in this case. In the context of http, it has a different meaning that does not concern DNS. EG: An http redirect tells a browser that hit www.domain1.com to go to www.domain2.com _at the HTTP level_. This is useful because it enables you to redirect, say, http://company.net/ to http://www.company.com/ and cause the location shown in the browser and remembered in bookmarks to change to http://www.company.com/. hope this helps, BM
