Date: Sun, 6 Nov 2005 18:22:58 -0600 From: Eric F Crist <ecrist@secure-computing.net> To: Paul Waring <paul@xk7.net> Cc: freebsd-questions@freebsd.org, "Edwin D. Vinas" <xmisoy@gmail.com> Subject: Re: how to setup DNS server and making sub-domains in DSL server Message-ID: <0358753F-3003-4A76-AC33-FB5BFBA2AEFE@secure-computing.net> In-Reply-To: <20051106224550.GA3718@kryten.xk7.net> References: <36f5bbba0511061138k4f9b5ef5q2fefed621c9ffc6b@mail.gmail.com> <436E60FC.5050009@makeworld.com> <20051106204732.GB755@kryten.xk7.net> <436E8682.5030306@makeworld.com> <20051106224550.GA3718@kryten.xk7.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 6, 2005, at 4:45 PM, Paul Waring wrote: > On Sun, Nov 06, 2005 at 04:41:06PM -0600, Chris wrote: >> It may not be necessary - but to do it right... I for one like to >> have >> mu IP's resolve both forward and reverse. It's just professional >> looking >> as a whole. > > I like to have my IPs resolve both ways too, but try finding an ISP > who > will either give you that sort of control through delegation or is > willing to setup the required reverse DNS records on their side. If > you're lucky you'll get customer114324.myisp.net to play with. I don't > know of any residential ISPs, at least not in the UK, who will do that > sort of thing. > > Having said that, there's nothing particularly "wrong" about not > having > reverse DNS records for IPs, or having ones that don't match. It only > really matters if you're sending out email to people with overly > aggressive spam filters that check for that sort of thing. > > Paul Actually, my ISP, ipHouse.net is one who's willing to configure reverse DNS for you. Qwest Communications is another one who'll setup DNS for you, and they're HUGE. If you choose to go with ipHouse, tell them I sent you -- then I get free DSL for a month! ----- Eric F Crist Secure Computing Networks http://www.secure-computing.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0358753F-3003-4A76-AC33-FB5BFBA2AEFE>