ns3 is now optional. Please remove it on DNS Edit page and try changing
nameservers with registrar/registry again.


On 09.12.08 13:19, "Edwin B." <[EMAIL PROTECTED]> wrote:

> 
> Hi Alex,
> 
> Well if I don't use NS3 it will include it because it's in the zone
> file or something. It then works as a hidden nameserver.
> 
> Regards
> 
> Edwin
> 
> On 9 dec, 10:24, Alex Kovalyov <[EMAIL PROTECTED]> wrote:
>> Yeah, SIDN are the most clever guys on the CCTLD market.
>> 
>> The interesting thing is:
>> Registry said that it does not have the domain and *does not relay*.
>> 
>>>     The SOA record of the requested domain was not found, because the
>>>     addressed server does not have it configured, and does not relay
>>>     the request either.
>> 
>> This 
>> tool:http://www.sidn.nl/ace.php/c,728,5886,,,,Nameserver_check.html?domain...
>> .net&primary=ns1.scalr.net&primary_ip=67.19.29.18&second1=ns2.scalr.net&seco
>> nd1_ip=67.19.90.82&second2=ns3.scalr.net&second2_ip=67.202.32.243&submit=Ver
>> zend
>> 
>> Says that ns3 *does relay* and it doesn't like it:
>> 
>> Error: name server at 67.202.32.243 is not authoritative.
>>     The SOA record for the domain was retrieved from the specified
>>     server, but that server answered only indirectly: it is not a
>>     source name server for this domain, but only relaying the query
>>     to other servers. This address must not appear in the TLD zone file.
>> 
>> ns3 is in fact a caching relay to ns1 and ns2.
>> 
>> Please use ns1 and ns2 only for now.
>> We're making so ns3 can be optionally removed from your zone on the Edit DNS
>> Zone page, for those captious registries that tend to analyze zone files on
>> nameservers.
>> 
>> On 08.12.08 21:35, "Edwin B." <[EMAIL PROTECTED]> wrote:
>> 
>> 
>> 
>>> Hi there,
>> 
>>> I tried adding an application with a .nl domain. After I created it, I
>>> assigned the nameservers to the domain. But the nameserver change is
>>> rejected by the SIDN (Dutch domain registry) because of a faulty
>>> ns3.scalr.net. I can't leave it out because it will add it in anyway.
>> 
>>> Response from SIDN:
>> 
>>> Errors=4, Warnings=2, Informational=1
>> 
>>> ** Summary: REJECTED ******.nl.
>> 
>>> Some problems need to get fixed:
>>>  - In total, 4 configuration errors where found.
>> 
>>> ** Full check report:
>> 
>>> * primary name server "ns1.scalr.net."
>> 
>>> *****.nl. 14400 IN SOA ns1.scalr.net.
>>>                                         admin.scalr.net.
>>>                                         (2008120802 4H 2H 1D 5M)
>>>   Warning: TTL of 5M in SOA is quite short; better at least 10M.
>>>     The shorter the time span in the TTL field of the SOA record, the
>>>     more often the SOA needs to be checked.
>>>     RIPE203 advises a TTL of 2D.
>> 
>>> hotnspicy.nl. 14400 IN NS ns3.scalr.net.
>>>   Warning: hidden name server "ns3.scalr.net." never used for first
>>> contact.
>>>     The zone contains an NS record for a host which is not in the list
>>> of
>>>     specified name servers. Hence, this name server will not be used
>>> to
>>>     initiate contact to the domain. It may be used in sequential
>>> lookups,
>>>     so it may still be useful.
>> 
>>> * secondary name server "ns2.scalr.net."
>>>   Info: name server looks correctly configured.
>> 
>>> * secondary name server "ns3.scalr.net." [HIDDEN]
>>>   Error: name server at 67.202.32.243 does not know about domain
>>> "*****.nl."
>>>     The SOA record of the requested domain was not found, because the
>>>     addressed server does not have it configured, and does not relay
>>>     the request either.
>>>   Error: name server "ns1.scalr.net." missing via IP 67.202.32.243
>>>     The primary name server listed this name server on its first IP-
>>> address.
>>>     However, this other source does not list that name.
>>>   Error: name server "ns2.scalr.net." missing via IP 67.202.32.243
>>>     The primary name server listed this name server on its first IP-
>>> address.
>>>     However, this other source does not list that name.
>>>   Error: name server "ns3.scalr.net." missing via IP 67.202.32.243
>>>     The primary name server listed this name server on its first IP-
>>> address.
>>>     However, this other source does not list that name.
>> 
>>> ** More information:
>>>   TE       refers to SIDN document "Technische Eisen" (Dutch only)
>>>            http://www.sidn.nl/doc/te.pdf
>>>   RFC1035  RFC "Domain Names - Implementation and Specifications"
>>>            http://rfc.net/rfc1035.html
>>>   RFC1123  RFC "Requirements for Internet Hosts
>>>            http://rfc.net/rfc1123.html
>>>   RFC1912  RFC "Common DNS Operational and Configuration Errors"
>>>            http://rfc.net/rfc1912.html
>>>   RFC3330  RFC "Special-Use IPv4 Addresses"
>>>            http://rfc.net/rfc3330.html
>>>   RIPE203  "Recommendations for DNS SOA Values"
>>>            http://www.ripe.net/ripe/docs/ripe-203.html
>> 
>>> ** DNScheck 4.2.4, 2008/12/08 20:29:07 CET+0100
>> 
>>> I hope you can help me with this....
>> 
>>> Regards,
>> 
>>> Edwin
> > 



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/scalr-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to