Hello. I have a problem with forwarding zone local to ISP resolvers.
My config is:
options {
directory /tmp;
disable-empty-zone .;
};
zone . {
type slave;
masters { 192.0.32.132; 193.0.14.129;};
masterfile-format text;
file /etc/bind/db.root;
I would imagine your issue is a lack of an NS delegation in the root zone
you are slaving. If you load a parent and then try to forward a child of
that parent you must have a delegation in the parent. The delegation
doesn't have to match the forwarders but it must exist.
On Mar 25, 2014 1:57 PM,
What happens if you remove the . after local?
On 03/25/14 12:57, Андрей Ветров wrote:
Hello. I have a problem with forwarding zone local to ISP resolvers.
My config is:
options {
directory /tmp;
disable-empty-zone .;
};
zone . {
type slave;
masters {
nothing, its correct name
2014-03-26 1:01 GMT+04:00 Lawrence K. Chen, P.Eng. lkc...@ksu.edu:
What happens if you remove the . after local?
On 03/25/14 12:57, Андрей Ветров wrote:
Hello. I have a problem with forwarding zone local to ISP resolvers.
My config is:
options {
.local is reserved for mDNS. I would say stop trying to use .local in
the DNS.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
Please visit
On 2014-03-25 16:16, Mark Andrews wrote:
.local is reserved for mDNS. I would say stop trying to use .local in
the DNS.
While true, I don't think it will help this particular issue. As I
understand it, BIND knows, by knowledge of being a root server, that
local. can't possibly exist, and so
6 matches
Mail list logo
