I see a couple of possible solutions to this. The first is a zone transfer,
but this might not work for you. This would provide you a copy of the remote
system's zone file on your system. The remote system would need to allow this
transfer (probably doesn't, remote admin would need to add your server to the
allowed list). Zone transfer entries are of a type slave in the named.conf
file:
zone example.local IN {
type slave;
masters {2001:db8::1};
file example.local;
};
You would then need to reload the zone files (rndc reload), or restart the
server.
http://www.microhowto.info/howto/configure_bind_as_a_slave_dns_server.html
Another option would be to tell bind to pass the request to another server.
Two methods of doing this are to forward (bind asks the other server to
resolve; could fail if not recursive), or to create a stub (local bind server
does the query):
zone example.local IN {
type forward;
forwarders {2001:db8::1};
};
zone example.local IN {
type stub;
masters {2001:db8::1};
file stub.example.local;
};
Again, you would need to reload zone files using rndc reload, or restart the
server.
On Sat, 21 Jun 2014 22:08:21 -0400
Ken D'Ambrosio k...@jots.org wrote:
Caveat: I'm a pretty good sysadmin, but DNS is one of my blind spots.
If I use incorrect terminology, please try to read for intent.
/whiney-assed attempt to explain this gaping hole in my knowledge
Hi -- using BIND, I'm trying to forward DNS queries for one (internal)
domain... well, internally. But it's not one I'm hosting, so I can't be
the master for it. All other queries, I want handled normally. I've
Googled/played around with various options parameters, but can't seem to
find the right magic sauce sequence.
Any pointers?
Thanks!
-Ken
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
signature.asc
Description: PGP signature
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
