dns issue, servfail
this issue has been bugging me for a while, it has no issues whatsoever upon the production, but i would just love to have those messages go away.[root@viper ~]# dig opyum.us @localhost
; <<>> DiG 9.3.3rc2 <<>> opyum.us @localhost
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 28364
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;opyum.us. IN A
;; Query time: 5 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Jan 7 15:53:02 2008
;; MSG SIZE rcvd: 26
BUT
[root@viper ~]# netstat -an |grep -w 53 |grep LISTEN
tcp 0 0 208.98.31.254:53 0.0.0.0:* LISTEN
tcp 0 0 208.98.31.253:53 0.0.0.0:* LISTEN
tcp 0 0 208.98.31.252:53 0.0.0.0:* LISTEN
tcp 0 0 208.98.31.251:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
i have my named.conf, an acl called "trusted" so my zones look like this:
acl "trusted" {
127.0.0.1;
208.98.31.252;
208.98.31.253;
208.98.31.254;
208.98.47.226;
};
127.0.0.1;
208.98.31.252;
208.98.31.253;
208.98.31.254;
208.98.47.226;
};
options
{
query-source port 53;
directory "/var/named"; // the default
dump-file "data/cache_dump.db";
statistics-file "data/named_stats.txt";
memstatistics-file "data/named_mem_stats.txt";
listen-on { 127.0.0.1; 208.98.31.254; 208.98.31.253; 208.98.31.252; 208.98.31.251; };
};
{
query-source port 53;
directory "/var/named"; // the default
dump-file "data/cache_dump.db";
statistics-file "data/named_stats.txt";
memstatistics-file "data/named_mem_stats.txt";
listen-on { 127.0.0.1; 208.98.31.254; 208.98.31.253; 208.98.31.252; 208.98.31.251; };
};
view "localhost_resolver"
{
match-clients { trusted; };
match-destinations { trusted; };
recursion yes;
zone "." IN {
type hint;
file "/var/named/named.ca";
};
include "/var/named/named.rfc1912.zones";
};
{
match-clients { trusted; };
match-destinations { trusted; };
recursion yes;
zone "." IN {
type hint;
file "/var/named/named.ca";
};
include "/var/named/named.rfc1912.zones";
};
view "internal"
{
match-clients { trusted; };
match-destinations { trusted; };
recursion yes;
zone "." IN {
type hint;
file "/var/named/named.ca";
};
{
match-clients { trusted; };
match-destinations { trusted; };
recursion yes;
zone "." IN {
type hint;
file "/var/named/named.ca";
};
view "external"
{
match-clients { any; };
match-destinations { any; };
recursion no;
zone "." IN {
type hint;
file "/var/named/named.ca";
};
{
match-clients { any; };
match-destinations { any; };
recursion no;
zone "." IN {
type hint;
file "/var/named/named.ca";
};
Jan 7 15:57:57 viper named[27746]: client 208.98.31.253#58576: view localhost_resolver: received notify for zone 'thing2.opyum.us': not authoritative
Jan 7 15:57:57 viper named[27746]: client 208.98.31.251#58576: view localhost_resolver: received notify for zone 'thing2.opyum.us': not authoritative
Jan 7 15:57:57 viper named[27746]: client 208.98.31.254#58576: view localhost_resolver: received notify for zone 'thing2.opyum.us': not authoritative
Jan 7 15:57:58 viper named[27746]: client 208.98.31.254#58576: view localhost_resolver: received notify for zone 'thing3.opyum.us': not authoritative
Jan 7 15:57:58 viper named[27746]: client 208.98.31.251#58576: view localhost_resolver: received notify for zone 'thing4.opyum.us': not authoritative
Jan 7 15:57:57 viper named[27746]: client 208.98.31.251#58576: view localhost_resolver: received notify for zone 'thing2.opyum.us': not authoritative
Jan 7 15:57:57 viper named[27746]: client 208.98.31.254#58576: view localhost_resolver: received notify for zone 'thing2.opyum.us': not authoritative
Jan 7 15:57:58 viper named[27746]: client 208.98.31.254#58576: view localhost_resolver: received notify for zone 'thing3.opyum.us': not authoritative
Jan 7 15:57:58 viper named[27746]: client 208.98.31.251#58576: view localhost_resolver: received notify for zone 'thing4.opyum.us': not authoritative