I have my Slackware Linux box connected to the outside world via a Speedtouch router. The router firewall is set up to allow incoming ssh and http connections to the Slackware box.
Currently my ADSL is UKFSN/ENTANet and I have a static IP address, the domain name is 84-45-228-40.no-dns-yet.enta.net.
I have a number of more useful/memorable/long-lived domains registered, some of which are hosted and some are not. Currently I have isbd.ltd.uk registered with justthename.co.uk and HTTP requests are redirected to 84-45-228-40.no-dns-yet.enta.net. This works sort of OK in the main but it's far from perfect because my Slackware box doesn't really know whether it's 84-45-228-40.no-dns-yet.enta.net or [www].isbd.ltd.uk.
What's the easiest and/or neatest way of sorting this out? Obviously my basic requirement is to make my slackware box think it's isbd.ltd.uk and to hide 84-45-228-40.no-dns-yet.enta.net completely.
I currently have www.isbd.ltd.uk in the following places on my slackware system:-
/etc/HOSTNAME /etc/hosts at the appropriate private IP address /etc/apache/httpd.conf as the ServerName value
However this causes various minor issues and infelicities, for example TWiki complains about a mismatch in the HTTP_HOST environment variable when run locally. I'd also prefer not to have to put 84-45-228-40.no-dns-yet.enta.net anywhere in HTML etc.
So, what's the proper and/or best and/or easiest way to sort this out? It's really only the HTTP issues that I want/need to resolve, can Apache virtual hosting do anything for me - I suspect not as that is only if I have multiple IP addresses *actually* resolving to my machine. I don't really want to go to the extent of making my Slackware machine host isbd.ltd.uk completely as that involves DNS, MX records and all sorts of complicated things like that. I just want 'transparent' forwarding of HTTP requests.
On 1/3/07, cl@isbd.net cl@isbd.net wrote:
Currently my ADSL is UKFSN/ENTANet and I have a static IP address, the domain name is 84-45-228-40.no-dns-yet.enta.net.
What's the easiest and/or neatest way of sorting this out? Obviously my basic requirement is to make my slackware box think it's isbd.ltd.uk and to hide 84-45-228-40.no-dns-yet.enta.net completely.
Will your ISP change the reverse DNS for your IP address? This will get rid of the less friendly name you currently have. You need to arrange for your chosen name to point to the IP address and they will change the IP address to resolve to your chosen name.
How much control do you have of isbd.ltd.uk DNS entries?
Good luck, Tim.
On Wed, Jan 03, 2007 at 11:15:44AM +0000, Tim Green wrote:
On 1/3/07, cl@isbd.net cl@isbd.net wrote:
Currently my ADSL is UKFSN/ENTANet and I have a static IP address, the domain name is 84-45-228-40.no-dns-yet.enta.net.
What's the easiest and/or neatest way of sorting this out? Obviously my basic requirement is to make my slackware box think it's isbd.ltd.uk and to hide 84-45-228-40.no-dns-yet.enta.net completely.
Will your ISP change the reverse DNS for your IP address? This will get rid of the less friendly name you currently have. You need to arrange for your chosen name to point to the IP address and they will change the IP address to resolve to your chosen name.
How much control do you have of isbd.ltd.uk DNS entries?
I can add/delete/modify A and CNAME and MX records.
Can I simply add a CNAME record that points www.isbd.ltd.uk to 84-45-228-40.no-dns-yet.enta.net? (and remove the existing www A record)
cl@isbd.net wrote:
What's the easiest and/or neatest way of sorting this out? Obviously my basic requirement is to make my slackware box think it's isbd.ltd.uk and to hide 84-45-228-40.no-dns-yet.enta.net completely.
[...]
It's really only the HTTP issues that I want/need to resolve, can Apache virtual hosting do anything for me - I suspect not as that is only if I have multiple IP addresses *actually* resolving to my machine. [...]
HTTP/1.0 or later can cope fine with different web sites resolving to the same IP address. Learn about Apache Name-based Virtual Hosting at http://httpd.apache.org/docs/2.2/vhosts/name-based.html
It won't allow SSL services in a very neat way because there's a circular problem: server needs to know its own hostname before connection in order to use the right SSL certificate, but the hostname being requested is sent in the request after the connection is made.
Hope that gets you started,