The use of 7.7.7.7 and 9.9.9.9 was used for testing purpose. This test is
to cover the scenario, if I have a reverse lookup which is not configured
on 10.212.24.11, i was expecting it to return NXDOMAIN and have it cached.
This is not the ideal scenario of usage, but to check the condition, if i
On 20.08.13 15:42, sumsum 2000 wrote:
zone "7.7.7.7.in-addr.arpa" IN {
type forward;
forwarders {10.212.24.11;};
forward only;
};
On 20.08.13 21:19, Mark An
The forward zone is not for a zone cut in the DNS tree. As a result
the SOA record is above the "zone" and the SOA record gets ignored.
In practice almost all forwarded zones match a actual zone so the
returned SOA record is accepted.
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117,
[root@FF15763 var]# dig -x 7.7.7.7
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-16.mlos2 <<>> -x 7.7.7.7
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62698
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;7.7.7.7.in-add
On 20.08.13 15:42, sumsum 2000 wrote:
zone "7.7.7.7.in-addr.arpa" IN {
type forward;
forwarders {10.212.24.11;};
forward only;
};
and when i do dig -x 7.7
Hi,
I have the following zone configuration for forwarding DNS query
view "default" IN {
max-cache-ttl 604800;
max-ncache-ttl 10800;
zone "." IN {
type forward;
6 matches
Mail list logo
