Cannot resolve nominum.org: SERVFAIL

Unbound
1

% dig MX nominum.org

; <<>> DiG 9.7.3 <<>> MX nominum.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 12227
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;nominum.org. IN MX

;; Query time: 1 msec
;; SERVER: ::1#53(::1)
;; WHEN: Tue Feb 7 11:01:37 2012
;; MSG SIZE rcvd: 40

It works for my BIND resolvers. Restarting solved the problem. Log is attached:

Feb 7 11:01:37 batilda unbound: [17061:0] debug: validator[module 0] operate: extstate:module_state_initial event:module_event_new
Feb 7 11:01:37 batilda unbound: [17061:0] info: validator operate: query nominum.org. MX IN
Feb 7 11:01:37 batilda unbound: [17061:0] debug: iterator[module 1] operate: extstate:module_state_initial event:module_event_pass
Feb 7 11:01:37 batilda unbound: [17061:0] info: resolving nominum.org. MX IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: resolving (init part 2): nominum.org. MX IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: resolving (init part 3): nominum.org. MX IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: processQueryTargets: nominum.org. MX IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: new target ns2.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: new target ns1.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] debug: iterator[module 1] operate: extstate:module_state_initial event:module_event_pass
Feb 7 11:01:37 batilda unbound: [17061:0] info: iterator operate: query ns2.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: resolving ns2.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: resolving (init part 2): ns2.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: resolving (init part 3): ns2.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: processQueryTargets: ns2.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: skipping target due to dependency cycle (harden-glue: no may fix some of the cycles) ns2.staff.nominum.org. A IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: new target ns1.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] debug: iterator[module 1] operate: extstate:module_state_initial event:module_event_pass
Feb 7 11:01:37 batilda unbound: [17061:0] info: iterator operate: query ns1.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: resolving ns1.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: resolving (init part 2): ns1.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: resolving (init part 3): ns1.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: processQueryTargets: ns1.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: skipping target due to dependency cycle (harden-glue: no may fix some of the cycles) ns2.staff.nominum.org. A IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: skipping target due to dependency cycle (harden-glue: no may fix some of the cycles) ns1.staff.nominum.org. A IN
Feb 7 11:01:37 batilda unbound: [17061:0] debug: out of query targets -- returning SERVFAIL
Feb 7 11:01:37 batilda unbound: [17061:0] debug: return error response SERVFAIL
Feb 7 11:01:37 batilda unbound: [17061:0] debug: validator[module 0] operate: extstate:module_state_initial event:module_event_moddone
Feb 7 11:01:37 batilda unbound: [17061:0] info: validator operate: query ns1.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] debug: iterator[module 1] operate: extstate:module_wait_subquery event:module_event_pass
Feb 7 11:01:37 batilda unbound: [17061:0] info: iterator operate: query ns2.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: processQueryTargets: ns2.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] debug: out of query targets -- returning SERVFAIL
Feb 7 11:01:37 batilda unbound: [17061:0] debug: return error response SERVFAIL
Feb 7 11:01:37 batilda unbound: [17061:0] debug: validator[module 0] operate: extstate:module_state_initial event:module_event_moddone
Feb 7 11:01:37 batilda unbound: [17061:0] info: validator operate: query ns2.staff.nominum.org. AAAA IN
Feb 7 11:01:37 batilda unbound: [17061:0] debug: iterator[module 1] operate: extstate:module_wait_subquery event:module_event_pass
Feb 7 11:01:37 batilda unbound: [17061:0] info: iterator operate: query nominum.org. MX IN
Feb 7 11:01:37 batilda unbound: [17061:0] info: processQueryTargets: nominum.org. MX IN
Feb 7 11:01:37 batilda unbound: [17061:0] debug: out of query targets -- returning SERVFAIL
Feb 7 11:01:37 batilda unbound: [17061:0] debug: return error response SERVFAIL
Feb 7 11:01:37 batilda unbound: [17061:0] debug: validator[module 0] operate: extstate:module_wait_module event:module_event_moddone
Feb 7 11:01:37 batilda unbound: [17061:0] info: validator operate: query nominum.org. MX IN
Feb 7 11:01:37 batilda unbound: [17061:0] debug: cache memory msg=2200012 rrset=3674981 infra=1964631 val=530448

2

Hi Stephane,

What version of unbound is this? (I do not see it fallback to
parent-side of the delegation, but that could also be that verbosity is
not high enough (or syslog dropped lines)).

Nominum's NS set looks OK now, here, although ns2 has 30 second TTL and
differs in parent and child side of the delegation. The 81.200.68.219
(ns2 parent side) is not working (timeout). Is there some sort of
nameserver maintenance going on?

Best regards,
   Wouter

3

a message of 109 lines which said:

What version of unbound is this?

1.4.14

4

Zitat von "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Stephane,

What version of unbound is this? (I do not see it fallback to
parent-side of the delegation, but that could also be that verbosity is
not high enough (or syslog dropped lines)).

Nominum's NS set looks OK now, here, although ns2 has 30 second TTL and
differs in parent and child side of the delegation. The 81.200.68.219
(ns2 parent side) is not working (timeout). Is there some sort of
nameserver maintenance going on?

First (uncached) lookup needed 3 seconds to complete from different locations. Either they have a load problem or they are on maintenance. The website is not reachable either.

Regards

Andreas