From wbahati at afsat-ke.com Tue Jan 11 18:48:06 2005 From: wbahati at afsat-ke.com (Wycliffe Bahati) Date: 11 Jan 2005 20:48:06 +0300 Subject: [dns-wg] nameserve in root servers Message-ID: <1105465686.26866.19.camel@mzee.iwayafrica.com> Dear all I got one of my nameservers registered as an ip address in the root servers. I have since changed provider. The problem is that this IP is still stuck in the root servers. I am not sure how to go about this as most servers are being referenced to my old ip address for dns. Rgds ./bahati From robert+ripelists at martin-legene.dk Tue Jan 11 19:02:41 2005 From: robert+ripelists at martin-legene.dk (Robert =?iso-8859-1?Q?Martin-Leg=E8ne?=) Date: Tue, 11 Jan 2005 19:02:41 +0100 Subject: [dns-wg] nameserve in root servers In-Reply-To: <1105465686.26866.19.camel@mzee.iwayafrica.com> References: <1105465686.26866.19.camel@mzee.iwayafrica.com> Message-ID: <20050111180241.GB82478@kb.pinguino.dk> On Tue, Jan 11, 2005 at 08:48:06PM +0300, Wycliffe Bahati wrote: > I got one of my nameservers registered as an ip address in the root > servers. I have since changed provider. The problem is that this IP is > still stuck in the root servers. I am not sure how to go about this as > most servers are being referenced to my old ip address for dns. Hello. To change your glue in the root zone, you need to contact IANA. The easiest way, is to use IANAs template for changing your TLD registration data and then specify as a purpose that server X.Y.Z changed IP. I suppose you are working for a ccTLD. Go see http://www.iana.org/cctld/ section C. Just fill out section 1, 2 and specify all name server data for all servers in sections 6a, 6b, 7a, 7b. Regards, -- robert @ dk From pk at TechFak.Uni-Bielefeld.DE Wed Jan 12 09:03:22 2005 From: pk at TechFak.Uni-Bielefeld.DE (Peter Koch) Date: Wed, 12 Jan 2005 09:03:22 +0100 Subject: [dns-wg] nameserve in root servers In-Reply-To: Your message of "11 Jan 2005 20:48:06 +0300." <1105465686.26866.19.camel@mzee.iwayafrica.com> Message-ID: <200501120803.j0C83Mr27062@zeder.TechFak.Uni-Bielefeld.DE> Hello, > servers. I have since changed provider. The problem is that this IP is > still stuck in the root servers. I am not sure how to go about this as > most servers are being referenced to my old ip address for dns. you are talking about addresses in root servers and about 'changing providers', which leaves ample room for speculation what the problem really is. Could you please tell us the name and address of said name server and one of the zones actually served by it? Thanks, Peter From wbahati at afsat-ke.com Wed Jan 12 09:10:20 2005 From: wbahati at afsat-ke.com (Wycliffe Bahati) Date: 12 Jan 2005 11:10:20 +0300 Subject: [dns-wg] nameserve in root servers In-Reply-To: <200501120803.j0C83Mr27062@zeder.TechFak.Uni-Bielefeld.DE> References: <200501120803.j0C83Mr27062@zeder.TechFak.Uni-Bielefeld.DE> Message-ID: <1105517419.2797.35.camel@mzee.iwayafrica.com> hi my probem is with a particular server kla1.afsat.com. If you check the root server have an ip address 62.128.174.1. It is now 62.128.168.70 so my problem is changing this there wycliffe On Wed, 2005-01-12 at 11:03, Peter Koch wrote: > Hello, > > > servers. I have since changed provider. The problem is that this IP is > > still stuck in the root servers. I am not sure how to go about this as > > most servers are being referenced to my old ip address for dns. > > you are talking about addresses in root servers and about 'changing providers', > which leaves ample room for speculation what the problem really is. > Could you please tell us the name and address of said name server and one of > the zones actually served by it? > > Thanks, > Peter From zsako at banknet.net Wed Jan 12 09:31:31 2005 From: zsako at banknet.net (Janos Zsako) Date: Wed, 12 Jan 2005 09:31:31 +0100 (MET) Subject: [dns-wg] nameserve in root servers Message-ID: <200501120831.j0C8VVxZ020544@banknet.banknet.net> > From dns-wg-admin at ripe.net Wed Jan 12 09:11:33 2005 Dear Wycliffe, > my probem is with a particular server kla1.afsat.com. If you check the > root server have an ip address 62.128.174.1. It is now 62.128.168.70 > so my problem is changing this there First of all, you are probably talking about _GTLD_ servers, not _root_ servers. There is no trace of kla1.afsat.com in the root servers, as far as I can tell. At the same time, kla1.afsat.com does not appear to be a glue in gtld-servers either. I see as glue: dar1.afsat.com. 172800 IN A 213.185.122.131 ns2.lightband.com. 172800 IN A 199.79.199.2 only. Please find below the full reply to the queries I used. Did I miss something? Best regards, Janos > > wycliffe > On Wed, 2005-01-12 at 11:03, Peter Koch wrote: > > Hello, > > > > > servers. I have since changed provider. The problem is that this IP is > > > still stuck in the root servers. I am not sure how to go about this as > > > most servers are being referenced to my old ip address for dns. > > > > you are talking about addresses in root servers and about 'changing providers', > > which leaves ample room for speculation what the problem really is. > > Could you please tell us the name and address of said name server and one of > > the zones actually served by it? > > > > Thanks, > > Peter $ host -d kla1.afsat.com k.root-servers.net ;; res_mkquery(0, kla1.afsat.com, 1, 1) ;; res_send() ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20538 ;; flags: rd; Ques: 1, Ans: 0, Auth: 0, Addit: 0 ;; QUESTIONS: ;; kla1.afsat.com, type = A, class = IN ;; Querying server (# 1) udp address = 193.0.14.129 ;; got answer, 504 bytes: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20538 ;; flags: qr rd; Ques: 1, Ans: 0, Auth: 13, Addit: 14 ;; QUESTIONS: ;; kla1.afsat.com, type = A, class = IN ;; AUTHORITY RECORDS: com. 172800 IN NS a.gtld-servers.net. com. 172800 IN NS g.gtld-servers.net. com. 172800 IN NS h.gtld-servers.net. com. 172800 IN NS c.gtld-servers.net. com. 172800 IN NS i.gtld-servers.net. com. 172800 IN NS b.gtld-servers.net. com. 172800 IN NS d.gtld-servers.net. com. 172800 IN NS l.gtld-servers.net. com. 172800 IN NS f.gtld-servers.net. com. 172800 IN NS j.gtld-servers.net. com. 172800 IN NS k.gtld-servers.net. com. 172800 IN NS e.gtld-servers.net. com. 172800 IN NS m.gtld-servers.net. ;; ADDITIONAL RECORDS: a.gtld-servers.net. 172800 IN A 192.5.6.30 a.gtld-servers.net. 172800 IN AAAA 2001:503:a83e::2:30 g.gtld-servers.net. 172800 IN A 192.42.93.30 h.gtld-servers.net. 172800 IN A 192.54.112.30 c.gtld-servers.net. 172800 IN A 192.26.92.30 i.gtld-servers.net. 172800 IN A 192.43.172.30 b.gtld-servers.net. 172800 IN A 192.33.14.30 b.gtld-servers.net. 172800 IN AAAA 2001:503:231d::2:30 d.gtld-servers.net. 172800 IN A 192.31.80.30 l.gtld-servers.net. 172800 IN A 192.41.162.30 f.gtld-servers.net. 172800 IN A 192.35.51.30 j.gtld-servers.net. 172800 IN A 192.48.79.30 k.gtld-servers.net. 172800 IN A 192.52.178.30 e.gtld-servers.net. 172800 IN A 192.12.94.30 ;; Query failed, 0 answers, status: no error kla1.afsat.com A record currently not present at k.root-servers.net $ host -d kla1.afsat.com a.gtld-servers.net ;; res_mkquery(0, kla1.afsat.com, 1, 1) ;; res_send() ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20539 ;; flags: rd; Ques: 1, Ans: 0, Auth: 0, Addit: 0 ;; QUESTIONS: ;; kla1.afsat.com, type = A, class = IN ;; Querying server (# 1) udp address = 192.5.6.30 ;; got answer, 127 bytes: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20539 ;; flags: qr rd; Ques: 1, Ans: 1, Auth: 2, Addit: 2 ;; QUESTIONS: ;; kla1.afsat.com, type = A, class = IN ;; ANSWERS: kla1.afsat.com. 172800 IN A 62.128.174.1 ;; AUTHORITY RECORDS: afsat.com. 172800 IN NS dar1.afsat.com. afsat.com. 172800 IN NS ns2.lightband.com. ;; ADDITIONAL RECORDS: dar1.afsat.com. 172800 IN A 213.185.122.131 ns2.lightband.com. 172800 IN A 199.79.199.2 ;; Query done, 1 answer, status: no error kla1.afsat.com A 62.128.174.1 $ host -d -a afsat.com a.gtld-servers.net ;; res_mkquery(0, afsat.com, 1, 255) ;; res_send() ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20543 ;; flags: rd; Ques: 1, Ans: 0, Auth: 0, Addit: 0 ;; QUESTIONS: ;; afsat.com, type = ANY, class = IN ;; Querying server (# 1) udp address = 192.5.6.30 ;; got answer, 134 bytes: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20543 ;; flags: qr rd; Ques: 1, Ans: 2, Auth: 2, Addit: 2 ;; QUESTIONS: ;; afsat.com, type = ANY, class = IN ;; ANSWERS: afsat.com. 172800 IN NS dar1.afsat.com. afsat.com. 172800 IN NS ns2.lightband.com. ;; AUTHORITY RECORDS: afsat.com. 172800 IN NS dar1.afsat.com. afsat.com. 172800 IN NS ns2.lightband.com. ;; ADDITIONAL RECORDS: dar1.afsat.com. 172800 IN A 213.185.122.131 ns2.lightband.com. 172800 IN A 199.79.199.2 ;; Query done, 2 answers, status: no error afsat.com NS dar1.afsat.com ;; res_querydomain(dar1.afsat.com, , 1, 1) ;; res_query(dar1.afsat.com, 1, 1) ;; res_mkquery(0, dar1.afsat.com, 1, 1) ;; res_send() ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20544 ;; flags: rd; Ques: 1, Ans: 0, Auth: 0, Addit: 0 ;; QUESTIONS: ;; dar1.afsat.com, type = A, class = IN ;; Querying server (# 1) udp address = 192.5.6.30 ;; got answer, 122 bytes: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20544 ;; flags: qr rd; Ques: 1, Ans: 1, Auth: 2, Addit: 2 ;; QUESTIONS: ;; dar1.afsat.com, type = A, class = IN ;; ANSWERS: dar1.afsat.com. 172800 IN A 213.185.122.131 ;; AUTHORITY RECORDS: afsat.com. 172800 IN NS dar1.afsat.com. afsat.com. 172800 IN NS ns2.lightband.com. ;; ADDITIONAL RECORDS: dar1.afsat.com. 172800 IN A 213.185.122.131 ns2.lightband.com. 172800 IN A 199.79.199.2 afsat.com NS ns2.lightband.com ;; res_querydomain(ns2.lightband.com, , 1, 1) ;; res_query(ns2.lightband.com, 1, 1) ;; res_mkquery(0, ns2.lightband.com, 1, 1) ;; res_send() ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20545 ;; flags: rd; Ques: 1, Ans: 0, Auth: 0, Addit: 0 ;; QUESTIONS: ;; ns2.lightband.com, type = A, class = IN ;; Querying server (# 1) udp address = 192.5.6.30 ;; got answer, 131 bytes: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20545 ;; flags: qr rd; Ques: 1, Ans: 1, Auth: 2, Addit: 2 ;; QUESTIONS: ;; ns2.lightband.com, type = A, class = IN ;; ANSWERS: ns2.lightband.com. 172800 IN A 199.79.199.2 ;; AUTHORITY RECORDS: lightband.com. 172800 IN NS deathstar.kersur.net. lightband.com. 172800 IN NS ns2.lightband.com. ;; ADDITIONAL RECORDS: deathstar.kersur.net. 172800 IN A 199.79.199.1 ns2.lightband.com. 172800 IN A 199.79.199.2 From wbahati at afsat-ke.com Wed Jan 12 09:40:38 2005 From: wbahati at afsat-ke.com (Wycliffe Bahati) Date: 12 Jan 2005 11:40:38 +0300 Subject: [dns-wg] nameserve in root servers In-Reply-To: <200501120831.j0C8VVxZ020544@banknet.banknet.net> References: <200501120831.j0C8VVxZ020544@banknet.banknet.net> Message-ID: <1105519237.2797.38.camel@mzee.iwayafrica.com> Hi This are the results I am getting if I do a dig +trace ;; Received 504 bytes from 192.5.5.241#53(F.ROOT-SERVERS.NET) in 1011 ms kla1.afsat.com. 172800 IN A 62.128.174.1 afsat.com. 172800 IN NS dar1.afsat.com. afsat.com. 172800 IN NS ns2.lightband.com. ;; Received 127 bytes from 192.33.14.30#53(B.GTLD-SERVERS.NET) in 866 ms see I got kla1 as 62.128.174.1 Rgds Wycliffe On Wed, 2005-01-12 at 11:31, Janos Zsako wrote: > > From dns-wg-admin at ripe.net Wed Jan 12 09:11:33 2005 > > Dear Wycliffe, > > > my probem is with a particular server kla1.afsat.com. If you check the > > root server have an ip address 62.128.174.1. It is now 62.128.168.70 > > so my problem is changing this there > > First of all, you are probably talking about _GTLD_ servers, not > _root_ servers. There is no trace of kla1.afsat.com in the root servers, > as far as I can tell. > > At the same time, kla1.afsat.com does not appear to be a glue in gtld-servers > either. I see as glue: > > dar1.afsat.com. 172800 IN A 213.185.122.131 > ns2.lightband.com. 172800 IN A 199.79.199.2 > > only. > > Please find below the full reply to the queries I used. > > Did I miss something? > > Best regards, > Janos > > > > > > wycliffe > > On Wed, 2005-01-12 at 11:03, Peter Koch wrote: > > > Hello, > > > > > > > servers. I have since changed provider. The problem is that this IP is > > > > still stuck in the root servers. I am not sure how to go about this as > > > > most servers are being referenced to my old ip address for dns. > > > > > > you are talking about addresses in root servers and about 'changing providers', > > > which leaves ample room for speculation what the problem really is. > > > Could you please tell us the name and address of said name server and one of > > > the zones actually served by it? > > > > > > Thanks, > > > Peter > > > $ host -d kla1.afsat.com k.root-servers.net > ;; res_mkquery(0, kla1.afsat.com, 1, 1) > ;; res_send() > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20538 > ;; flags: rd; Ques: 1, Ans: 0, Auth: 0, Addit: 0 > ;; QUESTIONS: > ;; kla1.afsat.com, type = A, class = IN > > ;; Querying server (# 1) udp address = 193.0.14.129 > ;; got answer, 504 bytes: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20538 > ;; flags: qr rd; Ques: 1, Ans: 0, Auth: 13, Addit: 14 > ;; QUESTIONS: > ;; kla1.afsat.com, type = A, class = IN > > ;; AUTHORITY RECORDS: > com. 172800 IN NS a.gtld-servers.net. > com. 172800 IN NS g.gtld-servers.net. > com. 172800 IN NS h.gtld-servers.net. > com. 172800 IN NS c.gtld-servers.net. > com. 172800 IN NS i.gtld-servers.net. > com. 172800 IN NS b.gtld-servers.net. > com. 172800 IN NS d.gtld-servers.net. > com. 172800 IN NS l.gtld-servers.net. > com. 172800 IN NS f.gtld-servers.net. > com. 172800 IN NS j.gtld-servers.net. > com. 172800 IN NS k.gtld-servers.net. > com. 172800 IN NS e.gtld-servers.net. > com. 172800 IN NS m.gtld-servers.net. > > ;; ADDITIONAL RECORDS: > a.gtld-servers.net. 172800 IN A 192.5.6.30 > a.gtld-servers.net. 172800 IN AAAA 2001:503:a83e::2:30 > g.gtld-servers.net. 172800 IN A 192.42.93.30 > h.gtld-servers.net. 172800 IN A 192.54.112.30 > c.gtld-servers.net. 172800 IN A 192.26.92.30 > i.gtld-servers.net. 172800 IN A 192.43.172.30 > b.gtld-servers.net. 172800 IN A 192.33.14.30 > b.gtld-servers.net. 172800 IN AAAA 2001:503:231d::2:30 > d.gtld-servers.net. 172800 IN A 192.31.80.30 > l.gtld-servers.net. 172800 IN A 192.41.162.30 > f.gtld-servers.net. 172800 IN A 192.35.51.30 > j.gtld-servers.net. 172800 IN A 192.48.79.30 > k.gtld-servers.net. 172800 IN A 192.52.178.30 > e.gtld-servers.net. 172800 IN A 192.12.94.30 > > ;; Query failed, 0 answers, status: no error > kla1.afsat.com A record currently not present at k.root-servers.net > > > > > > > $ host -d kla1.afsat.com a.gtld-servers.net > ;; res_mkquery(0, kla1.afsat.com, 1, 1) > ;; res_send() > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20539 > ;; flags: rd; Ques: 1, Ans: 0, Auth: 0, Addit: 0 > ;; QUESTIONS: > ;; kla1.afsat.com, type = A, class = IN > > ;; Querying server (# 1) udp address = 192.5.6.30 > ;; got answer, 127 bytes: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20539 > ;; flags: qr rd; Ques: 1, Ans: 1, Auth: 2, Addit: 2 > ;; QUESTIONS: > ;; kla1.afsat.com, type = A, class = IN > > ;; ANSWERS: > kla1.afsat.com. 172800 IN A 62.128.174.1 > > ;; AUTHORITY RECORDS: > afsat.com. 172800 IN NS dar1.afsat.com. > afsat.com. 172800 IN NS ns2.lightband.com. > > ;; ADDITIONAL RECORDS: > dar1.afsat.com. 172800 IN A 213.185.122.131 > ns2.lightband.com. 172800 IN A 199.79.199.2 > > ;; Query done, 1 answer, status: no error > kla1.afsat.com A 62.128.174.1 > > > > > > $ host -d -a afsat.com a.gtld-servers.net > ;; res_mkquery(0, afsat.com, 1, 255) > ;; res_send() > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20543 > ;; flags: rd; Ques: 1, Ans: 0, Auth: 0, Addit: 0 > ;; QUESTIONS: > ;; afsat.com, type = ANY, class = IN > > ;; Querying server (# 1) udp address = 192.5.6.30 > ;; got answer, 134 bytes: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20543 > ;; flags: qr rd; Ques: 1, Ans: 2, Auth: 2, Addit: 2 > ;; QUESTIONS: > ;; afsat.com, type = ANY, class = IN > > ;; ANSWERS: > afsat.com. 172800 IN NS dar1.afsat.com. > afsat.com. 172800 IN NS ns2.lightband.com. > > ;; AUTHORITY RECORDS: > afsat.com. 172800 IN NS dar1.afsat.com. > afsat.com. 172800 IN NS ns2.lightband.com. > > ;; ADDITIONAL RECORDS: > dar1.afsat.com. 172800 IN A 213.185.122.131 > ns2.lightband.com. 172800 IN A 199.79.199.2 > > ;; Query done, 2 answers, status: no error > afsat.com NS dar1.afsat.com > ;; res_querydomain(dar1.afsat.com, , 1, 1) > ;; res_query(dar1.afsat.com, 1, 1) > ;; res_mkquery(0, dar1.afsat.com, 1, 1) > ;; res_send() > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20544 > ;; flags: rd; Ques: 1, Ans: 0, Auth: 0, Addit: 0 > ;; QUESTIONS: > ;; dar1.afsat.com, type = A, class = IN > > ;; Querying server (# 1) udp address = 192.5.6.30 > ;; got answer, 122 bytes: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20544 > ;; flags: qr rd; Ques: 1, Ans: 1, Auth: 2, Addit: 2 > ;; QUESTIONS: > ;; dar1.afsat.com, type = A, class = IN > > ;; ANSWERS: > dar1.afsat.com. 172800 IN A 213.185.122.131 > > ;; AUTHORITY RECORDS: > afsat.com. 172800 IN NS dar1.afsat.com. > afsat.com. 172800 IN NS ns2.lightband.com. > > ;; ADDITIONAL RECORDS: > dar1.afsat.com. 172800 IN A 213.185.122.131 > ns2.lightband.com. 172800 IN A 199.79.199.2 > > afsat.com NS ns2.lightband.com > ;; res_querydomain(ns2.lightband.com, , 1, 1) > ;; res_query(ns2.lightband.com, 1, 1) > ;; res_mkquery(0, ns2.lightband.com, 1, 1) > ;; res_send() > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20545 > ;; flags: rd; Ques: 1, Ans: 0, Auth: 0, Addit: 0 > ;; QUESTIONS: > ;; ns2.lightband.com, type = A, class = IN > > ;; Querying server (# 1) udp address = 192.5.6.30 > ;; got answer, 131 bytes: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20545 > ;; flags: qr rd; Ques: 1, Ans: 1, Auth: 2, Addit: 2 > ;; QUESTIONS: > ;; ns2.lightband.com, type = A, class = IN > > ;; ANSWERS: > ns2.lightband.com. 172800 IN A 199.79.199.2 > > ;; AUTHORITY RECORDS: > lightband.com. 172800 IN NS deathstar.kersur.net. > lightband.com. 172800 IN NS ns2.lightband.com. > > ;; ADDITIONAL RECORDS: > deathstar.kersur.net. 172800 IN A 199.79.199.1 > ns2.lightband.com. 172800 IN A 199.79.199.2 > From bortzmeyer at nic.fr Wed Jan 12 09:49:27 2005 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Wed, 12 Jan 2005 09:49:27 +0100 Subject: [dns-wg] Re: nameserve in root servers In-Reply-To: <200501120831.j0C8VVxZ020544@banknet.banknet.net> References: <200501120831.j0C8VVxZ020544@banknet.banknet.net> Message-ID: <20050112084927.GA29915@nic.fr> On Wed, Jan 12, 2005 at 09:31:31AM +0100, Janos Zsako wrote a message of 216 lines which said: > At the same time, kla1.afsat.com does not appear to be a glue in gtld-servers > either. Sorry, you're wrong, it is indeed in the GTLD servers (not the root servers, as already mentioned) and your own test shows it: > $ host -d kla1.afsat.com a.gtld-servers.net ... > ;; flags: qr rd; Ques: 1, Ans: 1, Auth: 2, Addit: 2 ... > ;; ANSWERS: > kla1.afsat.com. 172800 IN A 62.128.174.1 From bortzmeyer at nic.fr Wed Jan 12 09:51:53 2005 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Wed, 12 Jan 2005 09:51:53 +0100 Subject: [dns-wg] Re: nameserve in root servers In-Reply-To: <1105519237.2797.38.camel@mzee.iwayafrica.com> References: <200501120831.j0C8VVxZ020544@banknet.banknet.net> <1105519237.2797.38.camel@mzee.iwayafrica.com> Message-ID: <20050112085153.GB29915@nic.fr> On Wed, Jan 12, 2005 at 11:40:38AM +0300, Wycliffe Bahati wrote a message of 233 lines which said: > see I got kla1 as 62.128.174.1 A simple whois shows that this machine has been registered in the ".com" nameservers (NOT the root nameservers) by the registrar Network Solutions. If you are a customer of Network Solutions, follow their procedures for changing that. If you used a reseller of Network Solutions, follow the procedures of the reseller. From ddiaz at satec.es Wed Jan 12 09:59:40 2005 From: ddiaz at satec.es (Daniel Diaz) Date: Wed, 12 Jan 2005 09:59:40 +0100 Subject: [dns-wg] nameserve in root servers Message-ID: <20050112085943.A4E7424D11@postman.ripe.net> Dear Wycliffe, (sorry for the last incomplete mail). As Janos explains, this has nothing to do with root-servers. In any case could be with the g-tld servers serving your parent zone (i.e. ".com", [a-m].gtld-servers.net.). I?ve just found this (see below) querying for "kla1" IP address, although this shouldn?t be the problem as kla1 is not auth., for "afsat.com."): ; <<>> DiG 8.3 <<>> @62.128.168.70 kla1.afsat.com <....> ;; ANSWER SECTION: kla1.afsat.com. 1d7h50m59s IN A 62.128.174.1 <...> as you see "kla1.afsat.com" replies that "kla1.afsat.com. has IP 62.128.174.1." any of your auth servers replies correctly with IN A 62.128.168.70. Querying any other dns server somehow gets 62.128.174.1. maybe wrong values used on SOA (i.e. too long and out-of-date data is still cached all around). I?ve also seen other little things like not including IN A RR for ns2 in the dar1.afsat.com.?s zone file for afsat.com. Hope this helps. My 2 cents. ; <<>> DiG 8.3 <<>> @62.128.168.70 kla1.afsat.com ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUERY SECTION: ;; kla1.afsat.com, type = A, class = IN ;; ANSWER SECTION: kla1.afsat.com. 1d7h50m59s IN A 62.128.174.1 ;; AUTHORITY SECTION: afsat.com. 7h51m7s IN NS dar1.afsat.com. afsat.com. 7h51m7s IN NS ns2.lightband.com. ;; ADDITIONAL SECTION: dar1.afsat.com. 23h52m43s IN A 213.185.122.131 ns2.lightband.com. 1d7h50m59s IN A 199.79.199.2 ;; Total query time: 1354 msec ;; FROM: nh to SERVER: 62.128.168.70 62.128.168.70 ;; WHEN: Wed Jan 12 09:46:08 2005 ;; MSG SIZE sent: 32 rcvd: 127 -- daniel.diaz -- Daniel D?az SATEC - Valencia http://www.satec.es C/. San Vicente Martir n?90,4? planta 46007 Valencia Mov.+34 600 990 335 Tel.+34 96 394 0076 Fax.+34 96 353 6730 From wbahati at afsat-ke.com Thu Jan 13 12:23:54 2005 From: wbahati at afsat-ke.com (Wycliffe Bahati) Date: 13 Jan 2005 14:23:54 +0300 Subject: [dns-wg] nameserve in root servers In-Reply-To: <20050111180241.GB82478@kb.pinguino.dk> References: <1105465686.26866.19.camel@mzee.iwayafrica.com> <20050111180241.GB82478@kb.pinguino.dk> Message-ID: <1105615434.3210.24.camel@mzee.iwayafrica.com> Hi all thanks everybody it was actually at the gtld and it was modified by network solutions tday Rgds Wycliffe On Tue, 2005-01-11 at 21:02, Robert Martin-Leg?ne wrote: > On Tue, Jan 11, 2005 at 08:48:06PM +0300, Wycliffe Bahati wrote: > > I got one of my nameservers registered as an ip address in the root > > servers. I have since changed provider. The problem is that this IP is > > still stuck in the root servers. I am not sure how to go about this as > > most servers are being referenced to my old ip address for dns. > > Hello. > > To change your glue in the root zone, you need to contact IANA. The > easiest way, is to use IANAs template for changing your TLD registration > data and then specify as a purpose that server X.Y.Z changed IP. > > I suppose you are working for a ccTLD. Go see http://www.iana.org/cctld/ > section C. Just fill out section 1, 2 and specify all name server data > for all servers in sections 6a, 6b, 7a, 7b. > > Regards, > > -- robert @ dk From kurtis at kurtis.pp.se Tue Jan 25 22:18:03 2005 From: kurtis at kurtis.pp.se (Kurt Erik Lindqvist) Date: Tue, 25 Jan 2005 22:18:03 +0100 Subject: [dns-wg] Re: ORSN-SERVERS.NET In-Reply-To: References: <005901c4b81b$40bccf80$6e8392d9@client.hildesheim.wfi.de> <00aa01c4b829$f0aebd50$6e8392d9@client.hildesheim.wfi.de> Message-ID: <990F319E-6F16-11D9-AF27-000A95928574@kurtis.pp.se> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2004-10-24, at 14.11, Kurt Erik Lindqvist wrote: My apologies for sending this mail. It has been sitting in a mailqueue with some other mails forever due to an error in my mail-server. Fixing that today apparently made it go out. I have no intention of reopening this debate and I think it was concluded a long time ago and it was never my intention to get into this again. Again, my apologies to all concerned. - - kurtis - -----BEGIN PGP SIGNATURE----- Version: PGP 8.1 iQA/AwUBQfa3k6arNKXTPFCVEQID5gCfaomCRSa6+dk786zbN0uB7HCuwhgAn3Hz VUL6NH90sZiemTfxfuWVIhCZ =roTQ -----END PGP SIGNATURE-----