Date: Wed, 24 Feb 2010 22:07:09 +0100 From: "Marcin M. Jessa" <lists@yazzy.org> To: lenz <norbu09@googlemail.com> Cc: FreeBSD-ISP <freebsd-isp@freebsd.org> Subject: Re: Registrars with free DynDNS services of my own domains. Message-ID: <4B8594FD.30406@yazzy.org> In-Reply-To: <e25246b61002241142w24fd185bn1f59d50818cc19d0@mail.gmail.com> References: <4B82F976.8020308@yazzy.org> <4B84E0B0.8070904@yazzy.org> <e25246b61002241142w24fd185bn1f59d50818cc19d0@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
lenz wrote: > if i may ... don't > > you miss a very important point here. DNS is bitch when it comes to > caching and large providers. never mind what you have as expire times > many large providers cache for a day to reduce their DNS traffic. if > you run a NS server on a dynamic IP this can be more of a lottery than > a solution. dyndns works fairly well for stuff that can live with > small expire times and is not mission critical. a ns record _is_ > mission critical as without it not only your website is offline but > potentially your mail other stuff. > > You're right and I am aware of it. The stuff I am hosting is websites with open source projects of mine and mostly my private stuff. Nothing of critical importance. Pluss my master DNS has a static IP. If anything changes, DNS lookups can be always made against it. > in your case i would get a cheap vhost somewhere and run the second ns > there (slicehost, smallest slice or such) and have a stable solution > or use the DNS from your provider or any other DNS hoster that offers > an API if you want to update records. I thought of it but I am willing to give my solution a shot before spending money on something that I may not need.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B8594FD.30406>