From M.Sabour at respina.net Wed Nov 6 14:31:22 2013 From: M.Sabour at respina.net (Mehdi Sabour) Date: Wed, 6 Nov 2013 17:01:22 +0330 Subject: [dns-wg] PTR Record Problem Message-ID: <24F25F71E5583446AE77C21A7EFD724650BC0651B5@exchange.respina.net> Dear Colleague, I have faced a problem and I want to address it to you; I hope you can help me. I have created 77.104.67.162 PTR record in my DNS Servers and make its domain in Ripe Database 67.104.77.in-addr.arpa on Monday 4th of November. However, DNS servers do not resolve this IP address. I checked this IP in my DNS Server and Ripe database and It seems everything is OK. I promise you can help me. Best Regards. --- Mehdi Sabour OC Manager Technical Division Respina Networks & Beyond T: +98 21 84 23 00 00 F: +98 21 88 19 10 83 www.respina.net ________________________________ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system administrator. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of RESPINA. Finally, the recipient should check this email and any attachments for the presence of viruses. RESPINA accepts no liability for any damage caused by any virus transmitted by this email. ________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmanning at isi.edu Thu Nov 7 09:14:26 2013 From: bmanning at isi.edu (manning bill) Date: Thu, 7 Nov 2013 00:14:26 -0800 Subject: [dns-wg] PTR Record Problem In-Reply-To: <24F25F71E5583446AE77C21A7EFD724650BC0651B5@exchange.respina.net> References: <24F25F71E5583446AE77C21A7EFD724650BC0651B5@exchange.respina.net> Message-ID: <89735C78-D2FF-4D30-81C5-251379826151@isi.edu> On 6November2013Wednesday, at 5:31, Mehdi Sabour wrote: > > Dear Colleague, > > I have faced a problem and I want to address it to you; I hope you can help me. > I have created 77.104.67.162 PTR record in my DNS Servers and make its domain in Ripe Database 67.104.77.in-addr.arpa on Monday 4thof November. However, DNS servers do not resolve this IP address. I checked this IP in my DNS Server and Ripe database and It seems everything is OK. I promise you can help me. > > Best Regards. > > > --- > Mehdi Sabour > OC Manager > Technical Division > Respina Networks & Beyond > T: +98 21 84 23 00 00 > F: +98 21 88 19 10 83 > www.respina.net > > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system administrator. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of RESPINA. Finally, the recipient should check this email and any attachments for the presence of viruses. RESPINA accepts no liability for any damage caused by any virus transmitted by this email. > well? $ dig 162.67.104.77.in-addr.arpa ; <<>> DiG 9.5.0-P1 <<>> 162.67.104.77.in-addr.arpa ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40647 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;162.67.104.77.in-addr.arpa. IN A ;; AUTHORITY SECTION: 77.in-addr.arpa. 3600 IN SOA pri.authdns.ripe.net. dns.ripe.net. 1383748256 3600 600 864000 7200 ;; Query time: 150 msec ;; SERVER: 198.32.2.10#53(198.32.2.10) ;; WHEN: Thu Nov 7 08:12:45 2013 ;; MSG SIZE rcvd: 104 tells me that RIPE has not delegated your prefix to your servers yet. /bill From romeo.zwart at ripe.net Thu Nov 7 09:26:56 2013 From: romeo.zwart at ripe.net (Romeo Zwart) Date: Thu, 07 Nov 2013 09:26:56 +0100 Subject: [dns-wg] PTR Record Problem In-Reply-To: <24F25F71E5583446AE77C21A7EFD724650BC0651B5@exchange.respina.net> References: <24F25F71E5583446AE77C21A7EFD724650BC0651B5@exchange.respina.net> Message-ID: <527B4ED0.1030500@ripe.net> Hello Mehdi, On 13/11/06 14:31 , Mehdi Sabour wrote: > > > Dear Colleague, > > I have faced a problem and I want to address it to you; I hope you can > help me. > > I have created 77.104.67.162 PTR record in my DNS Servers and make its > domain in Ripe Database 67.104.77.in-addr.arpa on Monday 4^th of > November. However, DNS servers do not resolve this IP address. I > checked this IP in my DNS Server and Ripe database and It seems > everything is OK. I promise you can help me. We will have a look at this asap. I suggest that we followup with you off-line. In future please direct operational requests at 'dns at ripe.net'. Kind regards, Romeo > > Best Regards. > > > > > > --- > Mehdi Sabour > > OC Manager > > Technical Division > Respina Networks & Beyond > T: +98 21 84 23 00 00 > F: +98 21 88 19 10 83 > www.respina.net > > > > ------------------------------------------------------------------------ > > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they are > addressed. If you have received this email in error please notify the > system administrator. Please note that any views or opinions presented > in this email are solely those of the author and do not necessarily > represent those of RESPINA. Finally, the recipient should check this > email and any attachments for the presence of viruses. RESPINA accepts > no liability for any damage caused by any virus transmitted by this email. > > ------------------------------------------------------------------------ > > > From zsako at iszt.hu Thu Nov 7 09:35:26 2013 From: zsako at iszt.hu (Janos Zsako) Date: Thu, 07 Nov 2013 09:35:26 +0100 Subject: [dns-wg] PTR Record Problem In-Reply-To: <89735C78-D2FF-4D30-81C5-251379826151@isi.edu> References: <24F25F71E5583446AE77C21A7EFD724650BC0651B5@exchange.respina.net> <89735C78-D2FF-4D30-81C5-251379826151@isi.edu> Message-ID: <527B50CE.50508@iszt.hu> Dear Mehdi, > $ dig 162.67.104.77.in-addr.arpa > tells me that RIPE has not delegated your prefix to your servers yet. The RIPE software does a lot of checks before delegating the reverse zone. As far as I can see, the RNAME in your SOA is incorrect (hostmaster.): $ host -t soa 67.104.77.in-addr.arpa. ns01.respina.net Using domain server: Name: ns01.respina.net Address: 77.104.106.2#53 Aliases: 67.104.77.in-addr.arpa has SOA record ns01.respina.net. hostmaster. 20130712 1800 600 1814400 3600 I suspect this is the cause of the denial of the delegation. Best regards, Janos Zsako From mir at ripe.net Tue Nov 12 16:16:18 2013 From: mir at ripe.net (Mirjam Kuehne) Date: Tue, 12 Nov 2013 16:16:18 +0100 Subject: [dns-wg] New on RIPE Labs: New gTLD Concerns: Dotless Names and Name Collisions Message-ID: <52824642.3080909@ripe.net> Dear colleagues, We published a new article by Geoff Huston on RIPE Labs: New gTLD Concerns: Dotless Names and Name Collisions https://labs.ripe.net/Members/gih/dotless-names In the long discussions about the new generic Top level Domains (gTLD), there were two technical topics that were the subject of many assertions and little in the way of observed data. The first concerned the viability of a so-called "dotless" name, where the gTLD label itself contains an IP address in the DNS, and the second concerns the concept of "name collisions" between existing local use of a name and the same name being delegated as a new gTLD. This article explores these two topics, and adds some data to the debate in the way of observed behaviours of the way common operating systems and browsers handle names. Kind Regards, Mirjam Kuehne RIPE NCC From anandb at ripe.net Fri Nov 15 15:59:40 2013 From: anandb at ripe.net (Anand Buddhdev) Date: Fri, 15 Nov 2013 15:59:40 +0100 Subject: [dns-wg] RIPE NCC Authoritative DNS service degraded Message-ID: <528636DC.70104@ripe.net> Dear colleagues, The RIPE NCC's authoritative DNS infrastructure is experiencing a very high query rate at the moment. This query rate is more than our routers can handle, and as a result, responses from our name servers are sporadic. We are working on mitigating this denial-of-service event. Please check our service outages page for updates. http://www.ripe.net/lir-services/service-announcements Regards, Anand Buddhdev RIPE NCC From marco.davids at sidn.nl Fri Nov 15 16:55:54 2013 From: marco.davids at sidn.nl (Marco Davids (SIDN)) Date: Fri, 15 Nov 2013 16:55:54 +0100 Subject: [dns-wg] RIPE NCC Authoritative DNS service degraded In-Reply-To: <528636DC.70104@ripe.net> References: <528636DC.70104@ripe.net> Message-ID: <5286440A.3050507@sidn.nl> Anand, Anand Buddhdev schreef op 15-11-13 15:59: > The RIPE NCC's authoritative DNS infrastructure is experiencing a very > high query rate at the moment. > http://www.ripe.net/lir-services/service-announcements Thank you for the heads-up. The information is not entirely clear to me. Is the K-root affected, or your 'ripe.net' authoritative servers? Thank you. -- Marco From bortzmeyer at nic.fr Fri Nov 15 17:22:33 2013 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Fri, 15 Nov 2013 17:22:33 +0100 Subject: [dns-wg] RIPE NCC Authoritative DNS service degraded In-Reply-To: <5286440A.3050507@sidn.nl> References: <528636DC.70104@ripe.net> <5286440A.3050507@sidn.nl> Message-ID: <20131115162233.GA3673@nic.fr> On Fri, Nov 15, 2013 at 04:55:54PM +0100, Marco Davids (SIDN) wrote a message of 19 lines which said: > The information is not entirely clear to me. Is the K-root affected, > or your 'ripe.net' authoritative servers? K-root appears to work fine (seen from several points or from DNSMON). I confirm the problem for pri.authdns.ripe.net or other 193.0.9.0/24 machines (they seem OK, now). From kranjbar at ripe.net Fri Nov 15 17:33:51 2013 From: kranjbar at ripe.net (Kaveh Ranjbar) Date: Fri, 15 Nov 2013 17:33:51 +0100 Subject: [dns-wg] RIPE NCC Authoritative DNS service degraded In-Reply-To: <5286440A.3050507@sidn.nl> References: <528636DC.70104@ripe.net> <5286440A.3050507@sidn.nl> Message-ID: <2f1fb40b02c3171d525377c9efb3762c@ripe.net> On 2013-11-15 16:55, Marco Davids (SIDN) wrote: ... > > The information is not entirely clear to me. Is the K-root affected, or > your 'ripe.net' authoritative servers? Hello Marco, It is not the K-Root. It is the authoritative DNS cluster that serves as primary for reverse DNS lookups for RIPE Region IP Resources as well as secondary for some ccTLDs. Latest news is that the attack is still ongoing but the rate seems to be decreased and we are working to clear out the rest. Just as a note the reverse zone has secondary on 4 different organisations, so it should not have visible effects for endusers. All the best, Kaveh. --- Kaveh Ranjbar, Chief Information Officer, RIPE NCC From cpetrie at ripe.net Fri Nov 15 18:06:54 2013 From: cpetrie at ripe.net (Colin Petrie) Date: Fri, 15 Nov 2013 18:06:54 +0100 Subject: [dns-wg] RIPE NCC Authoritative DNS service degraded In-Reply-To: <2f1fb40b02c3171d525377c9efb3762c@ripe.net> References: <528636DC.70104@ripe.net> <5286440A.3050507@sidn.nl> <2f1fb40b02c3171d525377c9efb3762c@ripe.net> Message-ID: <528654AE.90402@ripe.net> Dear colleagues, On 11/15/13 5:33 PM, Kaveh Ranjbar wrote: > Latest news is that the attack is still ongoing but the rate seems to be > decreased and we are working to clear out the rest. Query rates are now back at normal levels and service has been restored. However we will continue to monitor the situation. Regards, Colin Petrie RIPE NCC