Search Again: Re: RFC From: Michael McDonnell Date: Wednesday, November 4, 1998 Time: 1:28:00 pm Kirk, Rich Hackert at PSINet set mine up for me. He seems to have a good handle on this issue since I am using QuickDNS Pro and they are on a Unix box. Go ahead and email him and perhaps he can help you. hackertr@psi.com -Mike M. Kirk Samuelson said: >I've been meaning to write a word of thanks to Jeremy for helping me out >with this. Unfortunately the issue hasn't been resolved yet as nobody at our >ISP has any idea what I'm talking about. I forwarded them this message but >they didn't understand what they needed to do on their end to set this up. >Oh well... I assume I'm going to need them to correct their DNS records >before setting up reverse domains on our end will have any effect. > >I do appreciate the advice, though. > >Cheers, > >Kirk > >On Tuesday, November 3, 1998 8:34:09 PM, Chuck Rice wrote: > >> >>I need to do the same thing, and I was looking at your example but I could >>not figure where the 192 came from. Should that have been 231? -Chuck- >> >>At 08:56 PM -0500 1998/10/21, Mia's Virtual Post Office wrote: >> >>> >>> Lets say your IP range that your ISP delegated to you is from >>> 209.xxx.xx.231 to 209.xxx.xx.254 (24 block) >>> >>> Your ISP would have created a subdomain off of their network called >>> 0/24.192.xx.xxx.209.in-addr.arpa <This subnet example has two NS records:> >>> >>> NS isp.dns-server.com (your ISP's name server) >>> NS ns1.you.com (your name server) >>> >>> You will need to create a domain file called >>> "0/24.192.xx.xx.209.in-addr-arpa." on your server with the appropriate >>> PTR records for the subnet. >>> >>> 231.0/24.192.xx.xxx.209.in-addr.arpa. PTR real.name.com. >>> 232.0/24.192.xx.xxx.209.in-addr.arpa. PTR real.name.com. >>> 233.0/24.192.xx.xxx.209.in-addr.arpa. PTR real.name.com. >>> . >>> . >>> . >>> . >>> . >>> 254.0/24.192.xx.xxx.209.in-addr.arpa. PTR real.name.com. >>> >>> Make sure your ISP sets up their name server to act as secondary for this >>> subnet >>> 0/24.192.xx.xxx.209.in-addr.arpa with the IP address of your name server >>> ns1.you.com being 206.xxx.xx.231 >>> >>> Of course this is an example of IPs delegated off of a LAN. Your ISP more >>> than likely will give you an IP on their LAN for the server and then >>> delgate a /16 or whatever to that IP. However the example above should >>> apply. >>> >>> Beyond this, if your ISP/colo shop is adept enough, they should give you >>> the info you need to do this. >>> >>> Hope this helps.. >>> >>> >>> >>> Regards, >>> Jeremy Kinsey >>> WebMaster >>> >>> _______________________________________________________________________ >>> Mia.Net Maria's Internet Access >>> www.mia.net >>> Bella Mia, Inc. >>> N6015 Lyons Road e-mail: webmaster@mia.net >>> Burlington, WI. 53105 Phone: (414)763-5420 Fax: (414)763-5421 >>> ________________________________________________________________________ >>> Full Service Dial-In Internet Access >>> >>> Server CoLocation starts at only $150 per month! http://colocation.mia.net >> >>__________________________________________________________________________ >>Chuck Rice <mailto:Chuck@WildRice.com> >> >> >> > Michael R.N. McDonnell, Jr. michael@internetdesigncenter.com http://www.internetdesigncenter.com Tel: 941.430.1650 Fax: 941.430.1652 An online resource for Interior Designers and Architects Internet Design Center 2940 South Horseshoe Drive Suite 600 Naples, Florida 34104

Messages In This Thread: RFC by Michael McDonnell on Oct 20, 1998 at 1:24:00 pm Re: RFC by Chris Buxton on Oct 21, 1998 at 5:26:00 am Re: RFC by Mia''s Virtual Post Office on Oct 21, 1998 at 4:01:00 pm Re: RFC by Kirk Samuelson on Oct 22, 1998 at 12:59:00 am Re: RFC by Mia''s Virtual Post Office on Oct 22, 1998 at 1:56:00 am Re: RFC by Chuck Rice on Nov 4, 1998 at 2:34:00 am Re: RFC by Kirk Samuelson on Nov 4, 1998 at 3:39:00 am Re: RFC by Michael McDonnell on Nov 4, 1998 at 1:28:00 pm