Hello,

Ive been using DynDns for a few years now and it works really well. I run the ddclient on my web/mail server at home and update a dynamic free Account and also my custom account every 12 hours.

Im using IPCop for my firewall/router, which automatically detects the cycling of IP address by my ISP and updates the DynDns name server appropriatly.

I have no problems with delays in updates (or not that I have noticed). I guess if all is working as it should and normally does the DynDns servers map domains to IP addresses with a Time-to-Live of 60 seconds. So if your IP changes during mid visit, the maximum your site will be unavailable is less than 60 seconds. My isp cycles my ip every week or two ... you have to be unlucky to hit that exact moment.

The only problems Ive had are caused by my isp going funny, or when my USB modem and Linux decide its time for a reboot maybe once every few months of uptime.

Also, Since all the dns does is map IPs to Name and names to IPs, what you name your home domain and computers is irrelevent really, since your computer name is not reachable by name anyway, just by IP as far as your browser is concerend.

Really good service,

Hendrix

That's not quite the truth though. I made a production server with osCommerce installed on it. I needed a domain name and the way you assign your domain name and host does matter to a certain level. Since i'm using DynDNS Custom DNS service the scenario is described in the previous posts. Hosting Web w/Apache+PHP+MySQL is no prob but then when it's time to configure qmail, sendmail or your favorite then it's better to not misspell your host/domain or come up with something that doesn't exist. Anyways i think you know that just wanted to mention for any future post viewers/readers .

Yes and no to this also.
As stated in this thread previously it is not uncommon to use something other than .com/.net/.biz.org etc etc in the 24 bit part of a url such as mycpu.mydomain.myinitials (read as computer.myhomenet.sam) on a "private" There are a few post in the HOWTOs that even state this when setting up a private network.
WHY you may wonder? It is so on setting up ypur private network and providing such services as mail, www and such that you do not "step" on a real registered domain.
If you configure bind and DNS properly to use your ISPs dns server as bastion servers to yours then when you service a user your "made up" domain is properly identified across the net.
As I use a combine initials of mine and my husbands (.jnb) This shows up on everything we do and have. Including when we travel and use the laptops outside the core network.

Some important updates:
Few posts back i was explaining how i did the MX Records. Well it was not quite the correct settings. When you are making your MX Records you should comply with the following standard MX Rules:

• MX record cannot point to IP addresses
• If you create a single MX record, the priority doesn't matter
• If you create multiple MX records, your primary mail server must have the lowest preference
• Make sure not to create MX records backwards!

If you want mail for user@mydomain.com to go to myhost.mydomain.com, then you create the MX record for mydomain.com and set the Mail Exchanger field (if using the Basic interface) to myhost.mydomain.com with whatever priority you like. If you reverse the two DNS names, then you're telling remote servers where to send mail address to user@myhost.mydomain.com; In most cases this is not very useful.

Bottom line is -=> don't create MX Record for your main domain mydomain.com -=> just create one for your host myhost.mydomain.com where the mail server is configured.

laterz

Reading through this thread, I am not sure that there are any questions left. I just wanted to post to say that I have recently configured a Slackware box to be the web server and email server for my work using DSL, Slackware 10, ddclient, and dyndns.org . From my email headers, it appears that those of you who suggested that reverse DNS is controlled by your ISP and not changeable are RIGHT. This doesn't present a problem for me, as most people aren't reading the email headers. I have had no (OK, very few) problems with the entire setup. If any one is still needing help, please post your specific questions.

On a total side note, reading the posts from Nichole_knc , she is one of the sharpest posters on this board. All the newbies should do a search for the articles that she has authored and read up!!!

Good Luck,

This thread has been helpful for me - thanks all. In regards to the above situation, what do your "Host" records look like? I find it confusing on DynDns that you need to put what I call a Domain Name (mydomain.net) for a MX record under the column-title "Host," and the "Hostname" (myhost.mydomain.net) in the "data" column, yet the CNAME records require the opposite (Host = myhost.mydomain.net, Data = mydomain.com).

D.

I'm not sure this is the best place to ask this, but this seems like the most popular post about DynDNS.

You mention there is a delay and should not be used for apps other than personal - what do you say about using it to access professional IP CCTV cameras? Will the delay in propagation be a big issue here?

Has anyone had experience (or known of someone) with a huge, incovenient delay in DNS i.e. so much so that it would not be ideal for a CCTV security application?

Thanks

I don't know much at all about CCTV. The question you should ask is "Can my IP address change on me?" This is from their FAQ:

I don't think the "15-20 minute" delay is really that long, but it might be on occasion. Do you mind losing that much footage, or can your camera system hold onto it's data for that long?

Ideally, I think you would want to have a static IP. If you did that, you then wouldn't need dyndns.org, it would just be convenient.