[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Reverse Problem
- Subject: RE: [cobalt-users] Reverse Problem
- From: "E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>
- Date: Wed Apr 24 17:01:13 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
R> Date: Thu, 25 Apr 2002 06:46:19 +0800
R> From: Rick <rick@xxxxxxxxxxxx>
R> Im unsure how my uplink provider has deligated me the reverse authority
R> but, they asked me to put "bath" in front of my in.addr-pa
R> My Ip address is 202.126.189.250-254
Ah, I see. Yes, in order to easily delegate CIDR subnets, one
uses CNAMEs with some strange-looking zones. (The first time I
saw a "/" character in a zone, I nearly flipped. But it's
actually valid.)
Create a zone file for
bath.0.189.126.202.in-addr.arpa
In it, you need PTR records for
250 IN PTR host1
251 IN PTR host2
252 IN PTR host3
253 IN PTR host4
254 IN PTR host5
Or whatever the hosts are actually called.
Hmmmm. It looks like 202.126.189.254 might not be delegated
correctly, though. It has a different zone that's delegated
to ns.hotspeed.com.sg, unlike the others that are delegated to
ns1.sakon.com.sg -- which I presume to be correct.
It also looks like other 202.126.129.x IPs have been delegated to
you under different zones.
One no-no that I noticed: Your upstream(s) is/are chaining
multiple CNAMEs together. Recent versions of BIND [rightfully]
disallow this by default. Review RFC 2317 for more info...
--
Eddy
Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.