[gentoo-user] Bind problems when registering new domains....

2011-09-27 Thread Jens Reinemuth
Hi everybody,

i registered a new domain yesterday and tried to set the primary ans
secondary nameserver as usual, which resulted in the following
error-message:

Nameserver error - ERROR: 116 SOA record response must be authoritative
(resolver, answer)
([/10.121.46.9|/2001:608:6:7:5:0:0:11]=--80.239.175.176:53 (UDP,
PROTOCOL_EXPLICITLY_CHOSEN, Timeout: 3s, Retry: 1 x 0s, unsecure,
ignoreTC), [/10.121.46.9|/2001:608:6:7:5:0:0:11]=--80.239.175.176:53
(UDP, PROTOCOL_EXPLICITLY_CHOSEN, Timeout: 3s, Retry: 1 x 0s, unsecure,
ignoreTC): RA )

In the server there are 2 networking-interfaces, the ip-address of the
error belongs to the second one...


I am currently running bind-9.7.4 and did not change anything to the
config (except adding the new domain to the zones...)

As i am not really into the whole bind-thingy (someone configured it for
me...) i am totally stuck here...

Actually i tried to update bind to bind-9.8.1 and performed all the
chmods that were suggested, but no change... Still got the same errors.

Perhaps there is someone out there who can help me with this issue...

Regards,

Jens



Re: [gentoo-user] Bind problems when registering new domains....

2011-09-27 Thread Alan McKinnon
On Tue, 27 Sep 2011 09:10:53 +0200
Jens Reinemuth j...@reinemuth.info wrote:

 Hi everybody,
 
 i registered a new domain yesterday and tried to set the primary ans
 secondary nameserver as usual, which resulted in the following
 error-message:
 
 Nameserver error - ERROR: 116 SOA record response must be
 authoritative (resolver, answer)
 ([/10.121.46.9|/2001:608:6:7:5:0:0:11]=--80.239.175.176:53 (UDP,
 PROTOCOL_EXPLICITLY_CHOSEN, Timeout: 3s, Retry: 1 x 0s, unsecure,
 ignoreTC), [/10.121.46.9|/2001:608:6:7:5:0:0:11]=--80.239.175.176:53
 (UDP, PROTOCOL_EXPLICITLY_CHOSEN, Timeout: 3s, Retry: 1 x 0s,
 unsecure, ignoreTC): RA )


Is this for a .de zone?

Google returns many many hits for that error, all of them related
to .de somehow. This link seems to lay out the registrar rules nicely:

http://www.denic.de/en/background/name-server-service-of-denic/name-server-and-nsentry-data.html?cHash=3486f26050ac1dc3cbe6f5842dc70494

Your problem is certainly not related to bind itself, but to the data
in your zone file.  .de has a reputation of being somewhat ever-the-top
pedantic and your zone files seem to have something in them that the
registrar doesn't like.



 
 In the server there are 2 networking-interfaces, the ip-address of the
 error belongs to the second one...
 
 
 I am currently running bind-9.7.4 and did not change anything to the
 config (except adding the new domain to the zones...)
 
 As i am not really into the whole bind-thingy (someone configured it
 for me...) i am totally stuck here...
 
 Actually i tried to update bind to bind-9.8.1 and performed all the
 chmods that were suggested, but no change... Still got the same
 errors.
 
 Perhaps there is someone out there who can help me with this issue...
 
 Regards,
 
 Jens
 



-- 
Alan McKinnnon
alan.mckin...@gmail.com