About stop of messages which indicate refusing DNS NOTIFY from primary.
Issue
- Our customer has following dns servers.
Primary dns server 133.XX.YY.31 (2001:02F8:ZZ:AA::YY:31)
Secondary dns server 133.XX.YY.32(2001:02F8:ZZ:AA::YY:32)
- Under the environment, the following messages were logged in /var/log/messages on the secondary dns server.
zone XX.133.in-addr.arpa/IN/internal: refused notify from non-master: 2001:2f8:ZZ:AA::YY:31#60808: 1 Time(s)
zone xxx.yy.zz/IN/internal: refused notify from non-master: 2001:2f8:ZZ:AA::YY:31#60808: 1 Time(s)
zone xxx.zz/IN/internal: refused notify from non-master: 2001:2f8:ZZ:AA::YY:31#6169: 1 Time(s)
- It is configured as follows in 'named.conf ' on secondary. As you can see, only ipv4 address is defined in 'masters'.
zone "xxx.yy.zz" in {
type slave;
file "BACK/xxx.zone.in";
masters {
133.XX.YY.31;
};
zone "xxx.zz" in {
type slave;
file "BACK/xxx.zz.zone.in";
masters {
133.XX.YY.31;
};
zone "XX.133.in-addr.arpa" in {
type slave;
file "BACK/XX.133.rev.in";
masters {
133.XX.YY.31;
};
};
-
Questions
-
According to the customer, zone transfer works correctly in ipv4. Therefore, we believe these messages only indicates that the sercondary refused DNS NOTIFY from ipv6 address of primary dns server. Is our understanding correct?
-
Is there the way to stop the messages? We think that one way is that ipv6 address of primary dns server is specified in 'masters', but is there other way?
-
Environment
- Red Hat Enterprise Linux 6.5
- bind-9.8.2-0.23.rc1.el6_5.1.x86_64
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
