|
|
 |  |
Re: Setting Up Reverse DNS QueryFrom: Stuart Douglas Date: Wednesday, January 19, 2005
Time: 3:42:42 amHi
I changed the name of the primary domain 0.233.20.212.in-addr.arpa to
233.20.212.in-addr.arpa.groovychocolate.com as suggested but that meant that
the phrase '233.20.212.in-addr.arpa.groovychocolate.com ' was added to every
Parameter, both in the Domain information and Domain Window. forinstance,
in the Domain Informaiton window, the 'Primary' box was changed from
ns.groovychocolate.com
to
ns.groovychocolate.com.233.20.212.in-addr.arpa.groovychocolate.com
and 'Hostmaster' was changed from
hostmaster.groovychocolate.com
to
hostmaster.groovychocolate.com.233.20.212.in-addr.arpa.groovychocolate.com.
In the main Domain window, that made the PTR entry for our mailserver
82.233.20.212.in-addr.arpa.groovychocolate PTR
mail.groovychocolate.com.233.20.212.in-addr.arpa.groovychocolate.com.
which presumably isn't right. When I click on the Parameter 1 part of each
record to delete the 233.20.212.in-addr.arpa.groovychocolate.com. bit I
can't - all it let's me highlight and edit is the first
mail.groovychocolate.com part.
Sorry if I'm being dense, but this side of things is all new to me...
Also, we have QuickDNS Pro 2.2.1 - is there an upgrade?
Stuart
----------------------------------------------------------------------
Subject: Re: Setting Up Reverse DNS Query
From: "Stuart Douglas" <stuart@groovychocolate.com>
Date: Mon, 17 Jan 2005 16:00:07 -0000
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 |