Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DynDNS server 1
- Thread starter maya14
- Start date
What problem are you trying to solve? What is the driving force behind you considering hosting your own dynamic DNS server? I couldn't find anything on Google about "MintDynDNS". Are you trying to get into the Dynamic DNS business? If you are, there are many competitors for you out there already.
- Thread starter
- #3
We are in the cctc business and my boss wants to look at hosting our own DynDNS server. We are already using a DynDNS service. We want our clients to connect to our IP cameras as we dont have static IP's.MintDynDNS is software that allows you to host your own DynDNS server and clients can update their own records with client software. I just need to know how and where would i place this server in our excisting SBS 2003 network. We have only one public IP address which is dynamically assign to the router.
-
1
- #5
ShackDaddy
MIS
I don't think it's practical to try and host a DNS server at a dynamic address, since DNS propagation is too slow to make your DNS server reliably available to clients that need to register with it. I would really look into a cheap hosted server solution somewhere and host MintyDynDNS on that, or use an existing DynDns provider.
But assuming you want to try anyway, you can put the server in your internal network. I would advise not making it a member of your domain. Don't point your internal clients at it: make sure they still point at your SBS server for name resolution. Then allow inbound port 53 to the DynDNS server. You will also want to pick a custom port for MintyDynDNS to use (you don't want to use port 80 or 443), and allow that port access through your firewall to your DNS server. MintyDynDNS will listen on that port, and clients will use that port to update their DNS records. Normal DNS queries will come on port 53.
ShackDaddy
Shackelford Consulting
But assuming you want to try anyway, you can put the server in your internal network. I would advise not making it a member of your domain. Don't point your internal clients at it: make sure they still point at your SBS server for name resolution. Then allow inbound port 53 to the DynDNS server. You will also want to pick a custom port for MintyDynDNS to use (you don't want to use port 80 or 443), and allow that port access through your firewall to your DNS server. MintyDynDNS will listen on that port, and clients will use that port to update their DNS records. Normal DNS queries will come on port 53.
ShackDaddy
Shackelford Consulting
- Thread starter
- #6
The product i'm refering to is MintDNS. Anyway, i'm still unsure what network config etc must be in place to host such a DynDNS server.
Hardware specs/Static Public IP address/Registered domain name/Separate ADSL line/Traffic issues to DNS box??
How will clients find this DNS box on the Internet?
Hardware specs/Static Public IP address/Registered domain name/Separate ADSL line/Traffic issues to DNS box??
How will clients find this DNS box on the Internet?
ShackDaddy
MIS
The place where you registered your domain typically holds some entries for the name servers for the domain. Those entries have both names and IP addresses associated with them. So if you registered your domain name with Network Solutions, you can log in there and change the Name Servers.
Hardware specs are low, if all it's doing is handling DNS. An old workstation could be given a new powersupply and made to serve as your DNS server.
A static IP address should be on your priority list. Typically you can just ask your service provider for one and pay between $5 and $20 more per month for it.
I would have the MintDNS server's public name not be part of the domain that it's hosting, so that it doesn't have to be available to tell people about how to find itself. So if you have a couple of domain names, use one for your normal SBS network and give your DNS server a name in that domain. Then let your DNS server host a separate domain/zone for your dynamic clients to use.
You probably don't need an extra ADSL line, since the sort of traffic that this setup will generate won't be very high at all. Each time the server processes a renewal, I would guess there'd be less than 15k of back and forth traffic, and renewals won't even happen that often per client. You'll be able to monitor that and make a decision later if that's not true.
ShackDaddy
Shackelford Consulting
Hardware specs are low, if all it's doing is handling DNS. An old workstation could be given a new powersupply and made to serve as your DNS server.
A static IP address should be on your priority list. Typically you can just ask your service provider for one and pay between $5 and $20 more per month for it.
I would have the MintDNS server's public name not be part of the domain that it's hosting, so that it doesn't have to be available to tell people about how to find itself. So if you have a couple of domain names, use one for your normal SBS network and give your DNS server a name in that domain. Then let your DNS server host a separate domain/zone for your dynamic clients to use.
You probably don't need an extra ADSL line, since the sort of traffic that this setup will generate won't be very high at all. Each time the server processes a renewal, I would guess there'd be less than 15k of back and forth traffic, and renewals won't even happen that often per client. You'll be able to monitor that and make a decision later if that's not true.
ShackDaddy
Shackelford Consulting
- Thread starter
- #8
Serbtastic
Vendor
It uses port 80 to update its IP with DynDNS. Why would you block port 80?
- Status
Similar threads
- Locked
- Question
- Locked
- Question