Date: Thu, 21 Jul 2005 13:41:39 -0500 From: Kirk Strauser <kirk@strauser.com> To: freebsd-questions@freebsd.org Subject: Re: DNS service with a SQL backend Message-ID: <200507211341.43061.kirk@strauser.com> In-Reply-To: <op.st85lcwujjurwa@dyn94.dcjarmichael.com.au> References: <40356a66050720120219f6dd92@mail.gmail.com> <42DF4CAB.4070306@meijome.net> <op.st85lcwujjurwa@dyn94.dcjarmichael.com.au>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
On Thursday 21 July 2005 02:25, Daniel Marsh wrote:
> The only issue I foresee is having to have slightly different zone names
> that you wish to serve for each IP range.
Not true. Zone *files*, yes. Because of the wonderfulness that is NAT, my
LAN's nameserver gives different answers based on whether the query comes
from the LAN or the Internet. My named.conf looks similar to:
view "private" {
match-clients {
!127.0.0.1;
!::1;
localhost;
"lan";
};
zone "honeypot.net" {
type master;
file "internal/db.honeypot.net";
};
};
view "public" {
match-clients { any };
zone "honeypot.net" {
type master;
file "external/db.honeypot.net";
};
};
Then, my zone files looks like:
internal/db.honeypot.net:
$INCLUDE ../common-stuff
www IN A 10.5.0.32
external/db.honeypot.net:
$INCLUDE ../common-stuff
www IN A 12.34.56.78
common-stuff:
@ IN SOA ...
www IN A 2001:470:1f01:224:1::2
and so on
So, the Internet and my LAN see mostly the same data, except for a few
records that get answered with different values.
--
Kirk Strauser
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
iD8DBQBC3+xn5sRg+Y0CpvERAichAJ9yckILtA0fczFbcsJreLi6+Zy+XQCfR8dG
qd+0jvSPKuiikzT8Mv6Wz6U=
=X6aH
-----END PGP SIGNATURE-----
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507211341.43061.kirk>