New nameservers

spirit

Verified User
Joined
Nov 27, 2004
Messages
195
Location
Germany - Bremen
I have setup new nameserver on my server. but i get an error.

errors=4, warnings=2, informational=0
* domein webhosting010.nl.
* nameserver ns3.webhosting010.nl./217.170.21.217
W SOA refresh (7200) < 4 uur (zie RFC1537)
E nameserver heeft geen A/glue record [webhosting010.nl. NS ns3.webhosting010.nl.]
E nameserver heeft geen A/glue record [webhosting010.nl. NS ns4.webhosting010.nl.]
* nameserver ns4.webhosting010.nl./217.170.21.218
W SOA refresh (7200) < 4 uur (zie RFC1537)
E nameserver heeft geen A/glue record [webhosting010.nl. NS ns3.webhosting010.nl.]
E nameserver heeft geen A/glue record [webhosting010.nl. NS ns4.webhosting010.nl.]
 
Did you register the nameserver(s) at your registrar? You need to register the nameserver(s) at the same registrar where the domain they're part of is registered (if I can make out your Dutch, then this is probably the nameserver where webhosting010.nl is registered), to create a glue record or records.

Jeff
 
Hi,

For SIDN (the dutch registry) you do not have to register your nameservers first, however your nameservers must resolve.

The problem is that ns3.webhosting010.nl and ns4.webhosting010.nl do not resolve to IP's, see below...

=======
>ping ns1.webhosting010.nl

Pinging ns1.webhosting010.nl [65.98.61.11] with 32 bytes of data:

Reply from 65.98.61.11: bytes=32 time=119ms TTL=47
Reply from 65.98.61.11: bytes=32 time=119ms TTL=47
Reply from 65.98.61.11: bytes=32 time=119ms TTL=47
Reply from 65.98.61.11: bytes=32 time=119ms TTL=47

Ping statistics for 65.98.61.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 119ms, Maximum = 119ms, Average = 119ms

>ping ns2.webhosting010.nl

Pinging ns2.webhosting010.nl [65.98.61.12] with 32 bytes of data:

Reply from 65.98.61.12: bytes=32 time=119ms TTL=52
Reply from 65.98.61.12: bytes=32 time=118ms TTL=52
Reply from 65.98.61.12: bytes=32 time=119ms TTL=52
Reply from 65.98.61.12: bytes=32 time=121ms TTL=52

Ping statistics for 65.98.61.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 118ms, Maximum = 121ms, Average = 119ms

>ping ns3.webhosting010.nl
Ping request could not find host ns3.webhosting010.nl. Please check the name and try again.

>ping ns4.webhosting010.nl
Ping request could not find host ns4.webhosting010.nl. Please check the name and try again.

========

Once the 2 entries resolve the errors should dissapear.

regards,
Onno Vrijburg
 
Last edited:
Okay, let's go through a scenario...

Your domain is example.nl and the nameservers are ns1.example.nl and ns2.example.nl.

You register a domain, example.com, with two nameservers, ns1.example.nl and ns2.example.nl.

Your would-be site visitor tries to vist www.example.com.

His resolver tries to find the IP# for www.example.com, and can't find it.

So it asks the root-servers.

The root-servers don't have www.example.com in memory, so they refer the resolver to ns.domain-registry.nl (among others)

Neither ns.domain-registry.nl nor the others have www.example.com in their cache either, so they refer the resolver to ns1.example.nl and ns2.example.nl.

What IP# do they use to find ns1 and ns2.example.nl if they don't have A records themselves (when you register a nameserver with a registry, what you're doing is creating A records, at the root domain's nameservers. These are called glue records.

And if the glue records don't exist, either the resolver get's referred back to the Internet root-servers, or return an error message. If they return an error message, it's generally something about glue records not being available; if they refer back to the Internet root-servers, then the request eventually times out.

Am I missing something as to how the .nl domain can do it if it doesn't know the ip#s of the nameservers?

Thanks.

Jeff
 
Hi Jeff,

You are absolutely correct that SIDN as managers of the .NL zone must have the IP's of your nameservers. However SIDN manages it differently to most other registrars I know.

With each domain registration you also supply 2 or 3 nameservers, including IP addresses. So when SIDN needs to find the nameservers for domain name example.nl they look in thier database for example.nl, get the nameserver entries belonging to that domain name (out of the same record), connects to the DNS server based on the IP and retrieves the requested A record from the DNS server and returns it to the person requesting the entry.

Onno
 
Back
Top