Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.protocols.tcp-ip    |    TCP and IP network protocols.    |    14,669 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 14,157 of 14,669    |
|    Tim K to glen herrmannsfeldt    |
|    Re: Reverse DNS optional?    |
|    13 Mar 15 02:05:49    |
      From: kelletim@gmail.com              On Monday, February 2, 2015 at 8:08:42 PM UTC-6, glen herrmannsfeldt wrote:       > I was wondering how reverse DNS is supposed to be used.       > Consider some choices:       >       > A: Nobody uses it, and it is a waste of time to set up the servers.              I'm not sure I understand ... if your network is private, you'll be using the       same servers you're using anyway. If it's public, they're your ISP's.              >       > B: Some do, some don't, don't be surprised if it doesn't work.       >       > C: Only hosts that make outgoing connections need DNS, don't waste       > the time otherwise.       >       > D: Hosts that make outgoing connections and router ports need rDNS.       >       > E: Every host (and each port of multi-homed hosts) should have rDNS,       > but the network police won't arrest you for not doing it.       >       > F: Network administrators who don't configure reverse DNS should       > be shot.              I agree! I always do, it decreases latency in user requests across the board,       and it adds up to a sizable difference. Laziness is the only reason I can       think of for not configuring it.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca