It's always truly static :) Nick Olsen Network Operations (855) FLSPEED x106
---------------------------------------- From: "Mark Spring" <m...@nktelco.net> Sent: Thursday, March 06, 2014 10:24 AM To: "WISPA General List" <wireless@wispa.org> Subject: Re: [WISPA] rDNS for customer IPs Seems to me you wouldn't want to run down the list and create rDNS in the blind that says static in it unless it is truly static. Mark Spring Systems Analyst New Knoxville Telephone Company 301 W. South St. New Knoxville, OH 45871 419.753.5000 This message and the file(s) attached are confidential and proprietary information of NKTelco for the sole use of the intended recipient. Any unauthorized review, distribution, disclosure, copying, use, or dissemination, either whole or in part, is strictly prohibited. Do not transmit these documents, in any form, to any third party without the expressed written permission of NKTelco. On Thu, Mar 6, 2014 at 8:56 AM, Nick Olsen <n...@flhsi.com> wrote: We have entries for all of our space that is like 4-2-2-1.static.flhsi.com. And will insert records for a customer at their request for their static IP's. Never seen a website query for PTR before it would serve a page. But nothing surprises me these days. We specifically used the word "Static" in the PTR record because we found some mail providers would reject mail from them if it didn't include that word. And it was worse if it included anything like "dynamic" "dyn". /YMMV Nick Olsen Network Operations (855) FLSPEED x106 ---------------------------------------- From: "Kristian Hoffmann" <kh...@fire2wire.com> Sent: Wednesday, March 05, 2014 5:07 PM To: "WISPA General List" <wireless@wispa.org> Subject: Re: [WISPA] rDNS for customer IPs It helps to include the word "static" in the PTR record. At least one RBL uses this as a litmus test for whether or not IPs are static vs. dynamic, and will add your addresses en masse to their dynamic address block lists. That is, if your give static IP addresses. -Kristian On 03/05/2014 01:16 PM, Chris Fabien wrote: Is it customary to provide rDNS for all customer public IP addresses? We just had a complaint of one particular website running very slow, our customer contacted the website owner who said it was because we needed to "fix" our rDNS. The website acts like it must be doing a rDNS lookup and waiting for it to time out before serving a page. We've not ever had this configured for customer IPs before. Are we supposed to? _______________________________________________ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless _______________________________________________ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
_______________________________________________ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless