Unable to point NS server...
Unable to point NS servers to DYNU because of inconsistency
- Home
- Control Panel
- Community Forum
- Services
- Dynamic DNS Service
- Unable to point NS servers to DYNU because of inconsistency
- Community Forum
- Unable to point NS servers to DYNU because of inconsistency
Topic: Unable to point NS servers to DYNU because of inconsistency
Unable to point NS servers to DYNU because of inconsistency
by Manuel Bacso on Wednesday, September 2, 2015
by Manuel Bacso on Wednesday, September 2, 2015
Hello, when pointing a .de domain to your NS Servers I get errors. All your NS Servers provide me with the following error:Inconsistent set of NS RRsDo you have any solution present for this?Best regards,Manuel Bacso
Reply with quote | Report
Re: Unable to point NS servers to DYNU because of inconsistency
by timothytw on Thursday, September 3, 2015
by timothytw on Thursday, September 3, 2015
'Inconsistent set of NS RRs' means that the nameserver entries (NS records) in the DNS entry for the corresponding domain do not match the nameservers specified for the domain. We have customers with .de domain names setting up our name servers without any issues, so it should not be an issue with our name servers. We suggest that you contact your domain registrar for assistance.
Reply with quote | Report
Re: Unable to point NS servers to DYNU because of inconsistency
by fkressmann on Thursday, April 2, 2020
by fkressmann on Thursday, April 2, 2020
Sorry for unearthing that thread but I got the same issue now. When trying to set the nameservers to ns10 and ns11, the german authority DENIC refuses the edit with the mentioned error.This is because ns10 and ns11 just declare ns1 to ns6 as nameservers, but not each other (ns7 to ns12). The german authority requires all given nameservers to match the servers returned in the NS section of every given server to be accepted as nameservers. This is crappy and complex (so very german :D)Do you have any idea to get this working? One option would be that every NS of Dynu declares all other NS (huge NS section in) or having two servers which just return each other and not all the other ones (complicated setup...)Would be a pitty having to use servers in the US for a german domain because the query time is MUCH faster. 30msec vs 170msec...The only option right now s to specify exactly ns1 to ns6, not more and not less to get it accepted by DENICRegards,Felix
Reply with quote | Report
Re: Re: Unable to point NS servers to DYNU because of inconsistency
by vesey on Thursday, April 2, 2020
by vesey on Thursday, April 2, 2020
fkressmann wrote:Sorry for unearthing that thread but I got the same issue now. When trying to set the nameservers to ns10 and ns11, the german authority DENIC refuses the edit with the mentioned error.This is because ns10 and ns11 just declare ns1 to ns6 as nameservers, but not each other (ns7 to ns12). The german authority requires all given nameservers to match the servers returned in the NS section of every given server to be accepted as nameservers. This is crappy and complex (so very german :D)Do you have any idea to get this working? One option would be that every NS of Dynu declares all other NS (huge NS section in) or having two servers which just return each other and not all the other ones (complicated setup...)It would be a pity having to use servers in the US for a german domain because the query time is MUCH faster. 30msec vs 170msec...The only option right now is to specify exactly ns1 to ns6, not more and not less to get it accepted by DENICRegards,Felix
Reply with quote | Report
Re: Unable to point NS servers to DYNU because of inconsistency
by fkressmann on Thursday, April 2, 2020
by fkressmann on Thursday, April 2, 2020
Oh now I get how Dynu works :DI now removed all NS entries and entered ns10 and ns11 (not ns1) and DENIC accepted the change. Wonderful :)Thanks for your help!
Reply with quote | Report
Author | Topic: Unable to point NS servers to DYNU because of inconsistency |
---|---|
Manuel Bacso Joined: 6/30/2015 |
Unable to point NS servers to DYNU because of inconsistency Wednesday, September 2, 2015 11:59 PM
Hello, when pointing a .de domain to your NS Servers I get errors. All your NS Servers provide me with the following error:Inconsistent set of NS RRsDo you have any solution present for this?Best regards,Manuel Bacso
|
timothytw Joined: 5/2/2002 |
Unable to point NS servers to DYNU because of inconsistency Thursday, September 3, 2015 10:15 AM
'Inconsistent set of NS RRs' means that the nameserver entries (NS records) in the DNS entry for the corresponding domain do not match the nameservers specified for the domain. We have customers with .de domain names setting up our name servers without any issues, so it should not be an issue with our name servers. We suggest that you contact your domain registrar for assistance.
|
fkressmann Joined: 4/1/2020 |
Unable to point NS servers to DYNU because of inconsistency Thursday, April 2, 2020 7:41 AM
Sorry for unearthing that thread but I got the same issue now. When trying to set the nameservers to ns10 and ns11, the german authority DENIC refuses the edit with the mentioned error.This is because ns10 and ns11 just declare ns1 to ns6 as nameservers, but not each other (ns7 to ns12). The german authority requires all given nameservers to match the servers returned in the NS section of every given server to be accepted as nameservers. This is crappy and complex (so very german :D)Do you have any idea to get this working? One option would be that every NS of Dynu declares all other NS (huge NS section in) or having two servers which just return each other and not all the other ones (complicated setup...)Would be a pitty having to use servers in the US for a german domain because the query time is MUCH faster. 30msec vs 170msec...The only option right now s to specify exactly ns1 to ns6, not more and not less to get it accepted by DENICRegards,Felix
|
vesey Joined: 6/23/2017 |
Unable to point NS servers to DYNU because of inconsistency Thursday, April 2, 2020 2:00 PM
|
fkressmann Joined: 4/1/2020 |
Unable to point NS servers to DYNU because of inconsistency Thursday, April 2, 2020 11:01 PM
Oh now I get how Dynu works :DI now removed all NS entries and entered ns10 and ns11 (not ns1) and DENIC accepted the change. Wonderful :)Thanks for your help!
|
It is currently Thursday, December 19, 2024 9:34 AM US Mountain Standard Time
Thursday, December 19, 2024 9:34 AM