[176705] in North American Network Operators' Group
Re: ASN Domain for rDNS
daemon@ATHENA.MIT.EDU (Rubens Kuhl)
Wed Dec 10 06:20:53 2014
X-Original-To: nanog@nanog.org
In-Reply-To: <4B4120B1642DCF48ACA84E4F82C8E1F601A7F1440B0C@EXCH>
Date: Wed, 10 Dec 2014 09:20:45 -0200
From: Rubens Kuhl <rubensk@gmail.com>
To: Kate Gerry <kate@quadranet.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
And considering browsers use domains to define whether to send cookies or
not along a request, not having access customers on the same domain of your
website is a security benefit.
Rubens
On Wed, Dec 10, 2014 at 3:13 AM, Kate Gerry <kate@quadranet.com> wrote:
> Short answer: I just like doing it.
>
> Long answer: It allows me to create as many hosts on a segregated domain
> instead of making my company DNS zone 3000 records long.
>
> -----Original Message-----
> From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Fred
> Sent: Tuesday, December 09, 2014 4:36 PM
> To: nanog@nanog.org
> Subject: Re: ASN Domain for rDNS
>
> I'd say this is mostly for whitelabelling reason rather than a technical
> one?
>
> Keefe John:
> > I've been seeing more and more carriers(and even small ISPs) using
> > asXXXX.net as their domain for rDNS on IP space. What are the pros
> > and cons for doing this versus using your primary business domain name?
> >
> > Keefe John
>