Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm currently in the process of moving all of our domains to our own nameservers. Which wasn't an issue until I hit our own .de domain. I (think I) understand the implications of having the NS inside it's own domain, hence the need for glue records.

Until yesterday, I would have assumed I have a pretty good understanding of Bind and DNS zones until I was presented with this error from the Denic nameserver predelegation check:

Inconsistent set of nameserver IP addresses (NS, provided glues, determined glues)

  • []
  • Default resolver determined: [], other resolvers determined: {[/2a01:4f8:d13:3c85:0:0:0:2, /]}

Inconsistent set of nameserver IP addresses (NS, provided glues, determined glues)

  • []
  • Default resolver determined: [], other resolvers determined: {[/2a00:1158:3:0:0:0:0:b6, /]}

Screenshot of the result

The support of my registrar is either far better educated than me or doesn't have a clue. Either way, they're avoiding my questions in regards to what this error means. They just tell me

Your nameserver has to return your own nameservers as the default resolver.

But that doesn't make any sense to me and they refuse to try to explain it any other way.

This is the head of my current zone file:

@               86400   IN SOA (
                                        2012070505 ; serial
                                        1d         ; refresh
                                        3h         ; retry
                                        4w         ; expiry
                                        1h )       ; minimum

                3600    IN NS 
                3600    IN NS 

                3600    IN MX 10
                3600    IN MX 20
                3600    IN MX 30

localhost       3600    IN A  
localhost       3600    IN AAAA         ::1
@               3600    IN A  
                3600    IN AAAA         2a00:1158:3::b6
*               3600    IN A  
                3600    IN AAAA         2a00:1158:3::b6

hetzner         3600    IN A  
hetzner         3600    IN AAAA         2a01:4f8:d13:3c85::2
cloud           3600    IN A  
cloud           3600    IN AAAA         2a00:1158:3::b6

; List all NS as A/AAAA record
ns              3600    IN A  
ns              3600    IN AAAA         2a00:1158:3::b6
ns1             3600    IN A  
ns1             3600    IN AAAA         2a00:1158:3::b6
ns2             3600    IN A  
ns2             3600    IN AAAA         2a01:4f8:d13:3c85::2

So, what is the problem with my zone? And what is the "default resolver"?

share|improve this question
up vote 4 down vote accepted

Your nameservers have AAAA records, but you didn't include the IPv6 addresses as glue records (hence the glue records are not consistent with the addresses returned by your nameserver). Running the check with both IPv4 and IPv6 addresses listed returns the following:

DEnic nameserver check

share|improve this answer
Now that's a load off my mind. Thanks a lot! The registrar does not support IPv6 glue records :( Should I drop the IPv6 addresses for my NS from my zone to make it comply again? – Oliver Salzburg Jul 5 '12 at 20:57
@OliverSalzburg If the check doesn't actually get enforced by the registrar you can leave the AAAA records, but you won't have IPv6-only DNS working if you can't have AAAA glue records. – mgorven Jul 5 '12 at 21:01
I know, it sucks :( Let me update my zone and give it another go. Thanks again – Oliver Salzburg Jul 5 '12 at 21:02

Shouldn't your SOA record look something like   IN SOA ...
share|improve this answer
I don't know, should it? To my understanding, it's substituted with the zone name defined in named.conf.local. "If no $ORIGIN directive is present - BIND synthesizes one from the value of the zone name in the named.conf file , for example:". Am I misunderstanding? I've always used @ as a placeholder here to easily duplicate zones for other domains. – Oliver Salzburg Jul 5 '12 at 19:47

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.