On Mon, 2003-09-08 at 05:17, Steve Phillips wrote: > At 00:00 8/09/2003 -0600, Rodolfo J. Paiz wrote: > [snippage] > >Maybe you can do it if reverse-round-robin-DNS exists, but so far as I > >know it doesn't and, in any case, you would get any name at random from > >that list for every request anyway, which is not what you want. Simply set > >the reverse DNS to something that makes sense to YOU: 99.99% the only > >check that is made for reverse DNS is that it exists, not that it matches > >with forward DNS in any way. > > I would echo everyone of these sentiments 100% - and then add that you > should also ensure that at least one of your forward entries do match your > reverse entry (does not particularly matter which one) as some systems > require that a reverse lookup match a forward lookup of the same name and > otherwise deny access to the service. (another check for careless admins > which is not particularly useful but people do anyway) > > >Again, our 100 domains run on about 30 IP addresses, and the reverse DNS > >on all 30 addresses is the same: "rita.otherdomain.com". No one has yet cared. > > This is also a very true point ! and the same holds for the "real" hostname > of the machine as it appears in your Received: headers.
good tips thanks. Bret -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
