AW: WARN: Glue at parent nameservers

[Kevin Darcy]

As the text says, this is normal when all of your nameserver names are 
in a different TLD than that of the delegated domain. You have a .com 
domain delegated to only .de nameservers.

You might get a little optimization by creating .com "duplicates" of 
those nameserver names. Then the glue can come directly from the .com 
servers without forcing resolvers to make extra lookups.

                                                                         
                        - Kevin

Liebing, Stefan wrote:
> Thanks in advance!
>
> The domain is for example icm2.com. 
> We have only .de DNS the underlying cause of "WARNING".
>
> Do I have some way to avoid the "WARNING"
>
> [STEFAN]
>
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] Im Auftrag von JINMEI Tatuya / ????
> Gesendet: Montag, 7. Juli 2008 19:50
> An: dnsmaster at eds.de
> Cc: bind-users at isc.org
> Betreff: Re: WARN: Glue at parent nameservers
>
> At Thu, 03 Jul 2008 10:00:56 +0200,
> "dnsmaster at eds.de" <dnsmaster at eds.de> wrote:
>
>   
>> I am not new in the list but that is my first question.
>>
>> I'm wondering if I have troble with .com domains.
>>
>> Message:
>> ----------------------------------------------------------------------------------------------------------------------
>> WARNING. The parent servers (I checked with k.gtld-servers.net.) are not 
>> providing glue for all your nameservers.
>> This means that they are supplying the NS records (host.example.com), 
>> but not supplying the A records (192.0.2.53),
>> which can cause slightly slower connections, and may cause 
>> incompatibilities with some non-RFC-compliant programs.
>> This is perfectly acceptable behavior per the RFCs.
>> This will usually occur if your DNS servers are not in the same TLD as 
>> your domain (for example,
>> a DNS server of "ns1.example.org" for the domain "example.com").
>> In this case, you can speed up the connections slightly by having NS 
>> records that are in the same TLD as your domain.
>> ----------------------------------------------------------------------------------------------------------------------
>>
>> Can I ignore this? or what can I do?
>>     
>
> I suspect no one can provide more useful advice than the "WARNING"
> itself unless you also provide the .com domain name in question.
>
> ---
> JINMEI, Tatuya
> Internet Systems Consortium, Inc.
>
>
>
>
>