From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RmASC-0002NL-1Y for garchives@archives.gentoo.org; Sat, 14 Jan 2012 20:43:56 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 04E5CE089B; Sat, 14 Jan 2012 20:43:40 +0000 (UTC) Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) by pigeon.gentoo.org (Postfix) with ESMTP id ED947E0712 for ; Sat, 14 Jan 2012 20:42:39 +0000 (UTC) Received: by werh12 with SMTP id h12so311881wer.40 for ; Sat, 14 Jan 2012 12:42:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:organization :x-mailer:mime-version:content-type:content-transfer-encoding; bh=Gz24QUJvq1OgDU39lhg8BlqoPAbfA8t9b3ii45I564Y=; b=wKeZ9/4CwlCNT41bkiGrhmXS7OyThHbngQpVxN7+csFdakSA4PiR7Ny0B4Rp/FBlz4 UmHVi/Z4py/MyzpK6XF8bS0jDhor/782tSyv2wHDrd0lzrb20mHI60DHAvHvK8jI+Xsb k3j44OpnJBtneYvXubldEVrKxrsBJU2a04a3E= Received: by 10.216.134.137 with SMTP id s9mr2528858wei.16.1326573759101; Sat, 14 Jan 2012 12:42:39 -0800 (PST) Received: from khamul.example.con (196-215-2-107.dynamic.isadsl.co.za. [196.215.2.107]) by mx.google.com with ESMTPS id t15sm3630710wiv.6.2012.01.14.12.42.35 (version=SSLv3 cipher=OTHER); Sat, 14 Jan 2012 12:42:37 -0800 (PST) Date: Sat, 14 Jan 2012 22:42:17 +0200 From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Managing rDNS with BIND Message-ID: <20120114224217.75153f41@khamul.example.con> In-Reply-To: References: <20120109000206.4ebab630@khamul.example.con> Organization: Internet Solutions X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.8; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 884b6d4f-4a63-4ffa-a543-96bcc9eed584 X-Archives-Hash: f1c47fa3fd31a06301b386e043f9b5d1 On Sat, 14 Jan 2012 13:35:16 -0600 Carlos Sura wrote: > On 8 January 2012 16:02, Alan McKinnon > wrote: > > > On Sat, 7 Jan 2012 09:45:44 -0600 > > Carlos Sura wrote: > > > > > Hello mates, > > > > > > I have a problem, my provider does not want to set rDNS to my IP's > > > since I have 5 IP's rotating for my server, I don't know why. So > > > he told me I can do this manually. > > > > > > So I've added this as a master zone: > > > $ttl 38400 > > > 80.236.109.in-addr.arpa. IN SOA dominio.dominio.com. > > > abuse.dominio.com. (notice that last digits are miss) > > > 1325905990 > > > 10800 > > > 3600 > > > 604800 > > > 38400 ) > > > 80.236.109.in-addr.arpa. IN NS dominio.dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR ns1.dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR ns2.dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR dominio.com. > > > xx.xx.xxx.xxx.in-addr.arpa. IN PTR mail.dominio.com. > > > > > > > > > But it does not reflect any change in any machine, just in the > > > local machine I get the answer, when I try in any other machine, > > > it still showing me the rDNS of my provider. > > > > > > The reason is quite simple and most sane ISPs will do it that way. > > > > rDNS is NOT your A records in reverse, and you have no right of > > access to the zone. > > > > in-addr.arpa serves an entirely different purpose, it documents the > > layout of the ISPs address space. Your 5 IPs have not been > > delegated to you and you do not own them per whois, they still > > belong to your ISP and are merely recorded in the ISP record as > > assigned for your use. > > > > Therefore the ISP will use their own documentation standards to > > determine what is in the rDNS zone. > > > > Additionally, delegating out a /29 is a gigantic pain in the arse > > and leads to an unmaintainable mess in very short order (so says > > the poor sucker that's had to fix it...). At work we never > > sub-delegate out rDNS to customers; but we do do it for downstream > > re-sellers as they are ISPs in the in own right. > > > > So your ISP is quite correct in what they are saying. However, I > > would like to see a clarification of what your support contact > > means when he says "do it manually" - that doesn't make any sense > > > > -- > > Alan McKinnon > > > > > > Hello Alan McKinnon, > > Thank you for your answer, I get you now you explained everything I > needed to know. About my ISP, they changed it for me, since I was > sending a lot of ticket support to them, because they have a poor > support, I understand they don't manage and help me with a lot of > things, basically I don't need them, the only thing I was asking for > is to set the rDNS for me, hopefully they did, cause I told them, > that I really don't understand what they mean by "do it by myself" > and I was reading all BIND ebook to understad how delegation works. > > Regards > Hi Carlos, I'm glad to hear you came right. Yes, having your ISP update their rDNS with your machine's name is the best solution all round. -- Alan McKinnnon alan.mckinnon@gmail.com