|
|
 |  |
Re: Setting Up Reverse DNS QueryFrom: Men & Mice Support Date: Monday, January 17, 2005
Time: 11:48:15 amThe reverse zone might at some point have been delegated as
0.233.20.212.in-addr.arpa. But now it's delegated as
233.20.212.in-addr.groovychocolate.com.
Remove the old reverse zone and recreate it as this latter name. You
can export the old zone first, and then import it as the new zone, if
you want to.
Make sure you have exactly one PTR record for your mail server's IP
address. PTR record should look like this (with fully qualified
names):
82.233.20.212.in-addr.groovychocolate.com. PTR mail.groovychocolate.com.
Chris Buxton
Men & Mice - Making DNS Easy
At 4:00 PM +0000 1/17/05, Stuart Douglas wrote:
>At 3:28 PM +0000 11/9/04, Stuart Douglas wrote:
>>From: "Men & Mice Support" <cbuxton@menandmice.com>
>>Date: Mon, 8 Nov 2004 09:46:00 -0800
>>
>>>Setting up reverse DNS records isn't as straightforward as it sounds.
>>>First, you must figure out if the reverse zone belongs to your server.
>>
>>>With a regular domain name, when you register the domain, it's
>>>delegated to your server. A reverse zone must be similarly delegated,
>>>but "registration" is typically handled with your ISP rather than
>>>with a central registrar.
>>
>>>I looked up the PTR record delegation for ns.groovychocolate.com. The
>>>ednet.co.uk servers do in fact delegate your reverse records to your
>>>server. The zone name (called "domain name" in QuickDNS Pro 2.x) is:
>>
>>>233.20.212.in-addr.groovychocolate.com.
>>
>>>Creative, and perfectly legal. You don't even need to separate these
>>>into a reverse zone if you don't want to - just create records like
>>>this for each of your IP addresses:
>>
>>>82.233.20.212.in-addr.groovychocolate.com. PTR mail.groovychocolate.com.
>>
>>Ah, I was doing fine until this point Chris - our mail server and
>>Quick DNS are both on the 82 box, so I've already got a record :
>>
>>82.233.20.212.in-addr.groovychocolate.com. PTR ns.groovychocolate.com
>>
>>Is it allowable to have both records, ie:
>>
>>82.233.20.212.in-addr.groovychocolate.com. PTR mail.groovychocolate.com
>>82.233.20.212.in-addr.groovychocolate.com. PTR ns.groovychocolate.com
>
>It's not against the rules, but it's a bad idea in this case. You
>should have just the one pointing to mail.groovychocolate.com.
>
>I thought I;d done this right after your help, but today when one of
>our users tried to mail someone at easy.com they got a bounce back
>from the email admin there saying that we did not in fact have
>Reverse DNS setup for our mail server.
>
>The situation with our DNS server (which I took over responsibility
>for when our CTO left) is as follows:
>
>We have two Primary Domains set up,
>
>groovychocolate.com
>0.233.20.212.in-addr.arpa
>
>Our mail server and DNS server both reside on a mac cube with IP
>212.20.233.82. In the Primary Domain groovychocolate.com, we have
>(amongst others) these records
>
>groovychocolate.com NS ns.groovychocolate.com
>groovychocolate.com MX 10 mail.groovychocolate.com
>mail.groovychocolate.com A 212.20.233.82
>ns.groovychocolate.com A 212.20.233.82
>web.groovychocolate.com CNAME ns.groovychocolate.com
>
>and in the Primary Domain 0.233.20.212.in-addr.arpa we have the
>following entries:
>
>82.0.233.20.212.in-addr.arpa PTR mail.groovychocolate.com
>
>I'm not entirely sure why there is a zero in the
>0.233.20.212.in-addr.arpa domain, but presumably that's required
>since it's always been there?
>
>Could someone suggest what we need to add (a CNAME to
>groovychocolate.com perhaps?)
>
>Regards
>
>Stuart
>
>
>D
|

Return to Digital Point Solutions' Home Page |