Confused about DNS and Domain with a Dynamic IP

[AsymptoticCoder]

I have a domain name, say mydomain.com, and would like to use it with my home network.

Since I have a Dynamic IP, I am using DynDNS' Custom DNS package. But this only forwards the top-level domain to my dynamic IP. I cannot specify anything further.

I would like to be able to access the computers on my network (which are behind a router/firewall) using an internal DNS name that I must setup.

For example, if I type in www.mydomain.com, the request will be forwarded to port 80 of my Linux server (Apache). If I type in xyz.mydomain.com, the request will be forwarded to the server xyz in my LAN.

I am confused about how I can do this. Any suggestions or advice? How can I set this up?

[pparks1]

You need to run your own DNS server on your internal network and set your clients up to use this DNS server to handle resolution for xyz.mydomain.com.

I pulled the following info from my Fedora Directory Service howto.
This assumes your linux box is 192.168.1.100.

You will also have to have bind installed. Check if installed with rpm -q bind. If not installed, yum install bind.

1.logon as root to perform the following steps
2.edit /etc/named.conf add the following inside of the OPTIONS section
forwarders {192.168.1.x;}; (replace the IPADDR with your normal DNS server, likely a router)
NOTE: this allows you to get access to the Internet
3.service named start
4.chkconfig named on
5.download webmin from www.webmin.com
6.install webmin with rpm -ivh webmin*.rpm
7.connect to http://192.168.1.100:10000 from a webbrowser
8.logon with your root user account and password
9.click on Servers, click on Bind DNS Server
10.click on Create Master Zone
11.choose Zone Type of Forward, Domain Name of xyz.mydomain.com, records file of Automatic, master server as linuxserver.mydomain.com, choose to Add NS record for master server, fill out the Email address and click on Create.
12.Click on the Address Link (big A), under name, put in linuxserver, for the Address use 192.168.1.100 and click on Create.
13.Click on return to zone list, scroll down to bottom of pages and click on Apply changes.

[bubazoo]

along these same lines,

I have a webserver at:

www.domain.com hosted by easyDNS

however, I setup virtual hosting in httpd.conf to point

www.domain.com/~username requests to
username.domain.com

using this bit of code

<VirtualHost *>

ServerName www.tcoburn.us
ServerAlias tcoburn.us *.tcoburn.us

RewriteEngine On
# Skip www.domain.com
RewriteCond %{HTTP_HOST} !^(www\.)
RewriteCond %{HTTP_HOST} ^([^.]+)\.tcoburn\.us
RewriteRule ^(.*)$  /home/%1/www$1

</VirtualHost>

all fine and dandy, except, at easyDNS, they don't support wildcard records,
*.domain.com CNAME records I mean,

is there a way around this? without having to specify a CNAME record for each user on my server?

[AsymptoticCoder]

Thanks! I will have to give this a try. Unfortunately the rpm command given for webmin isn't working on my FC3. I'll download it, extract etc. and try it out.

[cruiseoveride]

wats this avahi daemon used for, can i disable it, it takes soo long to start up

[Zotter]

You could just setup port redirection in your router as well.

All port 80 traffic goes to 192.168.0.5
All port 22 traffic goes to 192.168.0.4

etc...

Then setup CNAMEs to suite, but have them all point to your A name. So, www.mydomain.com points to mydomain.com that points to your public IP of 10.2.5.3 - which is owned by your router. HTTP request comes into the WAN port of your router, port 80 - router then forwards that to 192.168.0.5 port 80 - your web server on the LAN. Reply traffic is passed back through the router's NAT function - everyone is happy.

I do this with DI-604, 624s all the time (change the default NTP server from the built in to pool.ntp.org !!!)

[AsymptoticCoder]

Zotter: thanks for that suggestion. But if I wanted to route requests to ftp.domain.com to say 192.168.0.2:21 and requests to home.domain.com to say 192.168.0.3:1111, would that work? What would I have to do to get that to work?

pparks: It sounds like your suggestion may do what I am looking for. I will have to look into it and become more familiar with the DNS lingo.