North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Re: Fixing .com DNS glue records - who to contact?
- From: Jim Popovitch
- Date: Tue Aug 16 17:35:06 2005
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=QuyFxYj2OqWoCiwQQ8SCgMjZt8t1LpLcZDOmRSVRdrzylgTTA8MJpRrZ/cGOw2GJjNWDf5LTHjncFTzHMmmaX6gNB6J1n+uxNdJiFWltd4LfcembV6nWDpRp8M8ZUNd37OJJfNY/9+MFOjh67qUnz03Vny4o13mGh8u3WtUKRO4= ;
On Tue, 2005-08-16 at 17:19 -0400, Jim Popovitch wrote:
> On Tue, 2005-08-16 at 14:10 -0700, Matthew Elvey wrote:
> > A glue record for a .com domain (nextbus.com) is wrong, and I'm running
> > into a brick wall trying to get it fixed.
> The problem is that the A and PTR records for your domain servers don't
> match up. See the "Mismatched glue" section of your dnsreport.
Err, scratch that. I misread your post.
188.8.131.52.in-addr.arpa is an alias for \
184.108.40.206.64.in-addr.arpa domain name pointer ns.nextbus.com.
Is "220.127.116.11.64.in-addr.arpa" valid?
> I've got the same issue with some domains hosted over at Register.com's
> GPN (Global Partner Network) division. GPN outsources DNS to eNom
> (which is an excellent thing), but the default GPN DNS settings use
> dnsXX.gpn.register.com which has a PTR to dns1.name-services.com. I
> *think* that this is OK per RFC, would really like to hear some expert
> opinions on this however.
I still would like to understand this validity of this however. ;-_