Date: Wed, 12 Aug 1998 10:35:29 +1200 (NZST) From: Andrew McNaughton <andrew@squiz.co.nz> To: Jesse <j@lumiere.net> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: named sending out NOTIFY on alternate IP Message-ID: <Pine.BSF.3.96.980812102826.16671A-100000@aniwa.sky> In-Reply-To: <Pine.BSF.4.02.9808110051040.27714-100000@leaf.lumiere.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 11 Aug 1998, Jesse wrote: > Date: Tue, 11 Aug 1998 00:55:18 -0700 (PDT) > From: Jesse <j@lumiere.net> > To: freebsd-isp@FreeBSD.ORG > Subject: named sending out NOTIFY on alternate IP > > > Anyone know if it's possible to have named originate all outgoing > connections from an aliased IP? Such a NOTIFY's. I have my ns on its own > IP for portability, but it isn't the primary IP for the machine. When it > sends NOTIFYs to inform the secondary DNS server about DNS record changes, > the secondary DNS server always sees it as coming from a non-authorative > server since it's not coming from the ns IP. > > I know I can just add the primary DNS servers' IP to the secondary > servers' master server list, but that's just a work around. I'd prefer to > make it send out the NOTIFYs via the right IP. It'd also make it possible > to secure up my ipfw rules a bit more. > > If anyone has any ideas or comments, I'd appreciate it. Thanks. I don't know what arrangements are available under named, but you could set up something using ipfw and natd to change where the packets leave from. Again it feels like a workaround, but at least it's a workaround on the right machine, and should allow for the ipfw restrictions you want. Andrew 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?Pine.BSF.3.96.980812102826.16671A-100000>