Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!van-bc!skl From: skl@wimsey.bc.ca (Samuel Lam) Newsgroups: comp.protocols.tcp-ip.domains Subject: Re: DNS not working for ftp? Keywords: name server, ftp Message-ID: <1991May24.101913.24612@wimsey.bc.ca> Date: 24 May 91 10:19:13 GMT References: <1991May23.215801.25117@arc.ab.ca> Reply-To: skl@wimsey.bc.ca (Samuel Lam) Organization: Balliffe Intersystem, Vancouver, B.C., Canada Lines: 27 In article <1991May23.215801.25117@arc.ab.ca>, mallard@arc.ab.ca (Derek Mallard) wrote: >We have recently assumed authority for our domain, arc.ab.ca and *.arc.ab.ca. >I had thought that doing so would have allowed us to ftp to sites that >had in the past refused us access since we were not recognized. >Unfortunately it made no difference that I can see. ;-( >... >Can any body suggest what might be the problem? Yes. You need to setup the reverse lookup mappings for your machines in your reverse zone (144.128.in-addr.arpa) as well. You should first setup that zone in a similar manner to how you setup your forward zone (arc.ab.ca), then contact to have the 144.128.in-addr.arpa (note it's not 128.144.in-addr.arpa, the reversal is normal) zone delegated to you. Let me know if you need sample named files for setting up your reverse zone. Once you have your reverse zone established, those remote FTP sites which have been rejecting your calls would start accepting them. ...Sam --