At 07:53 PM 9/7/2001, you wrote:
I have a client who just broke down and paid for a dedicated IP
Any hints on the values I should use for TTL to have reasonable
DNS propogation before I move his domain to the dedicated IP?
Thanks
Thom
baltimoremd@xxxxxxxxxxxxxxx Thom LaCosta K3HRN Webmaster
http://www.baltimoremd.com/cobaltfacts/
Home of the CobaltFacts Web Ring - cobalt-ot and hosting-biz mailing lists
I don't think anyone can give you a real answer. I do not host my own dns. I use register.com and it has take no more than 24 hours for any I have changed. Some times there are a few stragglers that take longer to get theirs done. I was told that at one time the centuryinter.net was using parallel dns servers. This meant that at one time one was updated and then another time the other was updated. They never seemed to be synced. It was nice to see them get a consultant a few years ago and spend a bunch of money and get it fixed correctly. Basically propagation is suppose to take between 24 and 72 hours as I have read in the past.
I do believe that more problems occur the lower in the chain the dns starts at. That is if you host it yourself it then depends on each and every up level to update it. The real problem is that dns is designed to prorogate down and not really up. But we live in the real world and that means today internic does not get everything first and then let things flow down. We just have to wait for it to get pushed to top level servers and then flow back down. If it does not get all the way up, the old start repropogating down again and we start over until it gets done. As much as sometimes I would like to run dns, I have not found a real reason and leave mine with a top level company.