Depends on how many "A" records that you expose. In general, you pretty much MUST have PTR records for mail servers.
And for network debugging, you pretty much SHOULD have PTR records for your routers and layer-3 switches. That's pretty much the required set. I don't know how many people and places are going to support PTR records for IPv6. Comparatively speaking, it doesn't scale well with IPv6 and it's a bit of a hassle. That's one of those practices that will evolve as IPv6 begins to blossom. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Andrew S. Baker [mailto:[email protected]] Sent: Sunday, September 04, 2011 12:20 PM To: NT System Admin Issues Subject: Re: When DNS for your ISP goes down... >>So, if your ISP won't delegate, you're stuck doing two DNS updates whenever >>you change addresses on something that should have a reverse. And what percentage of the A records that you expose to the world need corresponding PTR records? ASB http://XeeMe.com/AndrewBaker Harnessing the Advantages of Technology for the SMB market... On Sat, Sep 3, 2011 at 11:57 PM, Kurt Buff <[email protected]<mailto:[email protected]>> wrote: So, if your ISP won't delegate, you're stuck doing two DNS updates whenever you change addresses on something that should have a reverse. That's less than ideal, and I'll bet it's also pretty common. o- I suppose that means you need to be picky about your ISP, if you're a business and have choices o- Gawd, I can't wait for IPv6 to blossom. That *might* help with this issue. Kurt On Sat, Sep 3, 2011 at 04:09, Paul Hutchings <[email protected]<mailto:[email protected]>> wrote: > It depends on your ISP and whether your netblock is tied to them. > > If you have PI (provider independent) space you can delegate the DNS servers > at the registry to whoever you wish. > > If you have PA (provider allocated) space you're left with your ISP and > whether they will delegate out your block or not. > > I've noticed that some DNS providers seem to charge a lot more for reverse > DNS than forward DNS. Not sure there's a technical reason for that tbh. > ________________________________________ > From: Kurt Buff [[email protected]<mailto:[email protected]>] > Sent: 03 September 2011 12:53 AM > To: NT System Admin Issues > Subject: Re: When DNS for your ISP goes down... > > On Fri, Sep 2, 2011 at 12:23, Ben Scott > <[email protected]<mailto:[email protected]>> wrote: >> On Thu, Sep 1, 2011 at 12:05 PM, Steven Peck >> <[email protected]<mailto:[email protected]>> wrote: >>> If you move your DNS now, your DNS will be ISP vendor >>> neutral/independent and that's something that can be done >>> easily now if your connectivity suffers in the future it's one less >>> thing to do later. >> >> +53 >> >> Having your DNS tied to your connectivity or web hosting provider is >> not good. Having it independent means you can change other things >> much easier. Highly recommended. >> >> For example: Suppose you're changing connectivity providers at the >> office hosting your mail. With independent DNS, you simply add a new >> A record and a new MX record, leaving the old records intact. You >> allow time to propagate. Then switch cables, then cancel the old >> service. Nobody even notices. >> >> -- Ben > > Forgive the ignorance, but where does this leave PTR records? > > Kurt > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
