Date: Fri, 8 Sep 2000 16:28:44 -0400 From: "Adam Herzog" <adam@neonline.net> To: "Jonathan M. Slivko" <jslivko@coresync.net>, <freebsd-isp@FreeBSD.ORG> Subject: RE: Another DNS Issue Message-ID: <NEBBIFPEELHOBEJJJJFFGEABCCAA.adam@neonline.net> In-Reply-To: <Pine.BSO.4.21.0009081308120.31025-100000@rocket.coresync.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I recently had to change the IP of our DNS server, and it wasn't any trouble at all; I was pleasantly surprised. I only had to change it for the server itself, not for the several hundred domains that used it. *phew* If for some reason, you wanted to keep it listed as the dns server, but be updated from somewhere else, you should look into using rsync combined with a cron job... It's unnecessary, as far as I can tell, but it works. -Adam -----Original Message----- From: owner-freebsd-isp@FreeBSD.ORG [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Jonathan M. Slivko Sent: Friday, September 08, 2000 4:10 PM To: freebsd-isp@FreeBSD.ORG Subject: Another DNS Issue I'm trying to do this: I want to make a nameserver thats already on the Internet and working properly, etc look to another machine to receive DNS updates. How can I do that without too much trouble, e.g. changing the DNS servers on InterNIC. -- Jonathan M. Slivko ---- Jonathan M. Slivko <jslivko@coresync.net> Technical Support: CoreSync Corparation NSI ID: JSR730 Want a reliable shells? check us out at http://www.coresync.net! ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NEBBIFPEELHOBEJJJJFFGEABCCAA.adam>