Allowed glue is addresses records of nameserver whose names are
below the delegating zones. Absolutely, 100% required, when the
nameserver's name is within or below the delegated zone and sibling
glue which are within or below another another zone delegated from
the parent zone. The latter are o
On Sun, Jun 19, 2011 at 10:37 AM, Michael Sinatra
wrote:
> On 06/18/11 19:22, Casey Deccio wrote:
>
>> In particular, if the
>> name of the name server is itself in the subzone, we could be faced with
>> the situation where the NS RRs tell us that in order to learn a name
>> server's address, we s
On 06/18/11 19:22, Casey Deccio wrote:
In particular, if the
name of the name server is itself in the subzone, we could be faced with
the situation where the NS RRs tell us that in order to learn a name
server's address, we should contact the server using the address we wish
to learn. To fix th
On Sat, Jun 18, 2011 at 4:22 PM, Michael Sinatra
wrote:
> Consider:
>
> baz.org. NS ns1.dns.podunk.edu.
> baz.org. NS ns2.dns.podunk.edu.
>
> and
>
> dns.podunk.edu. NS ns1.dns.podunk.edu.
> dns.podunk.edu. NS ns2.dns.podunk.edu.
>
> In theory, you "should" only need glue in podunk.edu, but pod
2011/6/19 David Miller :
>
> In the particular case of the OP - example.net. has name servers under
> example.com.
>
> To make lookups for records under example.net., resolvers walk the tree from
> "." to "net." and get NS records - ns1.example.com. and ns2.example.com.
>
> You can't insert glue re
2011/6/19 Michael Sinatra :
> On 06/18/11 15:23, Chris Thompson wrote:
>>
>
>> Of course, at the root zone level, *all* NS records need either
>> "required glue" or "sibling glue", because every single one of them
>> is somewhere under the root zone. At least, until the aliens contact
>> us and we
On 06/18/11 15:23, Chris Thompson wrote:
On Jun 18 2011, Michael Sinatra wrote:
In theory, you can insert glue records anywhere above the zone in
question. See RFC 2181, section 5.4.1.
As an example, glue for the servers adns1.berkeley.edu and
adns2.berkeley.edu exist in the root zone.
For "
On Jun 18 2011, Michael Sinatra wrote:
In theory, you can insert glue records anywhere above the zone in
question. See RFC 2181, section 5.4.1.
As an example, glue for the servers adns1.berkeley.edu and
adns2.berkeley.edu exist in the root zone.
For "fj", "hk", and "xn--j6w193g". These ar
On 06/18/11 10:26, David Miller wrote:
All domains, at every level, have to configure their records such that
the tree can be walked from root to their domain.
Follow the "."s.
For: this.long.chain.example.com.
com. must be delegated by .
example.com. must be delegated by com.
chain.example.c
On 6/18/2011 12:24 PM, Lyle Giese wrote:
On 06/18/11 09:30, Jorg W. wrote:
Greetings,
given my domain name is example.net, and my NS servers for
example.net are:
ns1.example.com
ns2.example.com
But, example.com itself's NS servers are the registrator's (for
example, godaddy's).
Under this
On Sat, June 18, 2011 18:34, Lyle Giese wrote:
> On 06/18/11 10:21, Sven Eschenberg wrote:
>> That is weird.
>>
>> When I use my own NSes under my own domain, I need to reg them to .org
>> NSes, when I use my registrars NSes I don't.
>>
>> There does not seem to be any technical reason for your sce
On Sat, June 18, 2011 18:24, Lyle Giese wrote:
> On 06/18/11 09:30, Jorg W. wrote:
>> Greetings,
>>
>> given my domain name is example.net, and my NS servers for example.net
>> are:
>>
>> ns1.example.com
>> ns2.example.com
>>
>> But, example.com itself's NS servers are the registrator's (for
>> exa
On 06/18/11 10:21, Sven Eschenberg wrote:
That is weird.
When I use my own NSes under my own domain, I need to reg them to .org
NSes, when I use my registrars NSes I don't.
There does not seem to be any technical reason for your scenario (imho).
Regards
-Sven
P.S.: A direct glue of course co
On 06/18/11 09:30, Jorg W. wrote:
Greetings,
given my domain name is example.net, and my NS servers for example.net are:
ns1.example.com
ns2.example.com
But, example.com itself's NS servers are the registrator's (for
example, godaddy's).
Under this case, I don't need any glue for ns[1-2].exam
That is weird.
When I use my own NSes under my own domain, I need to reg them to .org
NSes, when I use my registrars NSes I don't.
There does not seem to be any technical reason for your scenario (imho).
Regards
-Sven
P.S.: A direct glue of course could reduce the lookup path length and save
r
Greetings,
given my domain name is example.net, and my NS servers for example.net are:
ns1.example.com
ns2.example.com
But, example.com itself's NS servers are the registrator's (for
example, godaddy's).
Under this case, I don't need any glue for ns[1-2].example.com.
But why I still need to reg
16 matches
Mail list logo