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: Suresh Ramasubramanian
- Date: Wed Aug 17 00:24:15 2005
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lx+vsF1QIbnX+Ipi4qI5xKJin47k32ovzARrNsyxU78jDYp3pMUQuKW+n3TQ5lTTMYkLMvrn9AzFsEVwypqt45MUBiBttUOOWuaM4NcXoI99J+93r0UJ/aPnI3HLVl9iqMnRZJ6ogRvL4xuT8J+058k3qKTfKkplj+H+rEndiAY=
On 17/08/05, Jim Popovitch <firstname.lastname@example.org> wrote:
> 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.
Argh Argh Argh. We ran into that rather extensively and finally ended
up moving a bunch of domains that we run mail for to ultradns.