bind with my cable modem (that uses DHCP) 1

[venkman]

I'm interested in setting up a DNS on my LAN at home. I have a couple of computers which connect via a hub to another pc running ipchains/NAT, which in turn connects to my cable modem. Like most cable connections, mine is DHCP and the address is changed roughly once a month or once every other month. I have a registered domain name w/ verio, let's call it mydomain.com for now. Assuming Verio has my current IP address, when someone tries to access my computer via http or ssh or something else I allow, they can access it using mydomain.com. I would like people to be able to access my computers behind the firewall/gateway by doing something like pc1.mydomain.com or pc2.mydomain.com. I was thinking that if DNS gives port numbers also, I could use port-forwarding to accomplish this.... does it? Is there a way to do this? I'v never setup a DNS before, is there a good tutorial out there on this particular configuration?

Thanks,
Venkman

 

[sleipnir214]

I recommend you go to one of the DNS hosting providers (I use ZoneEdit:

http://www.zoneedit.com),

create yourself an account, set the servers of authority for your domain to the DNS provider's machines, then update your domain registration with Verio.

In order to host DNS yourself, your domain name server MUST have a static IP address. I suppose you could have it on DHCP, but every time the IP address changed, you would have to update your DN server's registration with your registar. That means anywhere from 12-24 hours for the registar to propagate the changes to the root DN servers, which translates to days of downtime from the time you discover the change to the IP address to the time the changes propagate to the root servers.

However, this still is not going to get people into all the machines on your network as is. The problem is you have multiple machines sharing a single IP address. There is no way for the firewall to know to which IP address it should send an external connection unless you set up port forwarding. ______________________________________________________________________
Never forget that we are
made of the stuff of stars

 

[venkman]

Sleipnir,

Thanks for responding to my post. I had not realized there was a serice that does dynamic DNS. Also, does DNS provide port numbers when it does a resolution or just IP Addresses? I do have some knowledge of NAT and could setup port-forwarding without a problem, so that's not an issue.

Cheers,
Venkman

 

[venkman]

Actually, I've thought of this some more, and I'm gussing DNS doesn't do ports. Otherwise what would it do with a request like mypc.mydomain.com:8080? Anyway, thank you for your help, I'll be sure to mark your response as helpful.

-Venkman

 

[GoldenEternity]

No, the best that DNS can do in that regard is respond with a certain class of server. For example, it will respond that the MX (Mail eXchange) for a domain is mail.example.com.

But it can't tell the client that the web server for

http://www.example.com

is on port 8080.

 

[MikeLacey]

We have a cable modem as well, and if we run a server (web, ftp, irc etc) our ISP get's soggy and hard to light.... Mike
________________________________________________________________

"Experience is the comb that Nature gives us, after we are bald."

Is that a haiku?
I never could get the hang
of writing those things.

 

[fluid11]

DNS uses port 53 to perform name resolution.

ChrisP If somebody helps you, please click the link in the botton left hand corner that says "Mark this post as a helpful/expert post".