Re: [WISPA] rDNS for customer IPs
If you use bind, there's need to do rDNS blindly. Use $GENERATE to have bind create them for you. Works on forward and reverse. My reverse entrys have one line defining all the ip's in that certain block On Thu, Mar 6, 2014 at 3:22 PM, Nick Olsen n...@flhsi.com wrote: 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 listWireless@wispa.orghttp://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 -- Micah Miller Network/Server Administrator Network Business Systems, Inc. Phone: 309-944-8823 ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] rDNS for customer IPs
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
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 listWireless@wispa.orghttp://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
Re: [WISPA] rDNS for customer IPs
All our customers are mostly static (powercode assigns static DHCP leases) but they occasionally change if we swap equipment etc. But I'm thinking for residential customers calling them dynamic would be more appropriate. On Thu, Mar 6, 2014 at 10:24 AM, Mark Spring m...@nktelco.net wrote: 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 listWireless@wispa.orghttp://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 ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
Re: [WISPA] rDNS for customer IPs
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
[WISPA] rDNS for customer IPs
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
Re: [WISPA] rDNS for customer IPs
We do a standard reverse record for all ip's so just come up with a generic entry that includes the ip. We ran into this on rare occasions and found this to be standard on our feelers. Mark On Wednesday, March 5, 2014, Chris Fabien ch...@lakenetmi.com 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? -- 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. ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
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
Re: [WISPA] rDNS for customer IPs
When you say the website acts like it's doing a RDNS lookup and waiting for a timeout, that sounds like key information. Even if you don't have PTR records for your customer IPs, you should be very quickly returning an NXDOMAIN for those queries. Do these PTR queries from the outside have a timeout condition as opposed to a quick NXDOMAIN? Does it perhaps wait a while and then return a SERVFAIL? If so, that could be the cause of your complaints. On Wed, Mar 5, 2014 at 3:16 PM, Chris Fabien ch...@lakenetmi.com 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
