Configuring Reverse Dns zone file

BOG junk at 1command.com
Tue Aug 10 10:56:23 UTC 2004


Greetings Chris,
 Nice name! Chris is also my name. :)
I see one problem right off the bat. Read a little further down...

chris.ngo at gmail.com (Chris Ngo) wrote in message news:<cdh5i9$2301$1 at sf1.isc.org>...
> Hi all,
> 
> Im trying to set my reverse dns. I have set my RDNS zone files, but
> when I dig my ip its doesnt show any of my PTR record.
> 
> [root at octopusmarketing pz]# cat 193.204.161.209.in-addr.arpa 
> $TTL 86400
> 
> @       IN      SOA     octopusmarketing.com.    cngo.emaylme.com. (
; Add these lines:
$ORIGIN   204.161.209.IN-ADDR.ARPA.
$TTL 86400
; Change (your) line above to:
@       IN      SOA     ns.octopusmarketing.com.    cngo.emaylme.com. (
; see the difference?
>                         1       ; Serial
>                         8H      ; Refresh
>                         2H      ; Retry
>                         1W      ; Expire
>                         1D)     ; Minimum TTL
; ADD THE FOLLOWING:
                          IN    NS    ns.octopusmarketing.com.
                          IN    A     209.161.204.193
> 
; I'm going to have to guess what the *actual* nubmer you are using
; for your mail servers. But based on your querry, they should be correct

1.204.161.209.IN-ADDR.ARPA.   IN   PTR   mail.investimmo.ca.
2.204.161.209.IN-ADDR.ARPA.   IN   PTR   mail.adjointeplus.ca.
193.204.161.209.IN-ADDR.ARPA.  IN   PTR     ns.octopusmarketing.com.
> 

Is your NET block this big? 209.161.204.1 - 209.161.204.193 and beyond?
I only used 1 and 2 for your mail servers based on the fact they were
already used. Now that I created a working IN-ADDR.ARPA. zone for you.
You can adjust the mail IP's if I guessed their IP's wrong. You can not
use 193.204.161.209.IN-ADDR.ARPA. as a RR because there are no
other addresses within it. The IN-ADDR.ARPA. zone indicates your NET block.
It starts on the NET number and ends on the BCAST. This is why I had to
chop the 193.204.161.209.IN-ADDR.ARPA. file off to 204.161.209.IN-ADDR.ARPA.
So that you can define the NET block *within* the zone. Otherwise, everything
would be *outside* the zone - which is why you had this problem.

Hope this clears things up.

Best wishes,
 Chris


> 
> 
> when using the dig command, no PTR records appear:
> wasabi at acura wasabi $ dig @209.161.204.193 -x 209.161.204.193
> 
> ; <<>> DiG 9.2.2rc1 <<>> @209.161.204.193 -x 209.161.204.193
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13666
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL:
> 0
> 
> ;; QUESTION SECTION:
> ;193.204.161.209.in-addr.arpa.  IN      PTR
> 
> ;; AUTHORITY SECTION:
> 193.204.161.209.in-addr.arpa. 86400 IN  SOA     octopusmarketing.com.
> cngo.emaylme.com. 1 28800 7200 604800 86400
> 
> ;; Query time: 62 msec
> ;; SERVER: 209.161.204.193#53(209.161.204.193)
> ;; WHEN: Sun Jul 18 15:10:05 2004
> ;; MSG SIZE  rcvd: 115
> 
> 
> 
> 
> Anyone?
> 
> thx


More information about the bind-users mailing list