Hey Reinier, > > > the .14 also works over TEAMS. The problem is with the whole subnet, > > > on SEACOM i can not even resolve names (like mctim, are you on the > > > same upstream?)
AFAIK, Seacom is not currently an ISP/upstream provider. Rather, they manage infrastructure (e.g. undersea cables) which ISPs (e.g. TATA) use to carry their traffic. Think UETCL. Tim, feel free to clean up if I've made a mess of things ;) Regards, Kyle Spencer ----- Original message ----- > Hi, > > This is all for sake of curiousity, and for the greater local hosting > (on an african level) good. > > By all means, go play golf :-) > > -- > rgds, > > Reinier Battenberg > Director > Mountbatten Ltd. > +256 758 801 749 > www.mountbatten.net > > > > On Monday 10 January 2011 09:06:39 McTim wrote: > > Reiner, > > > > is this idle curiosity or business critical? If the latter, i can > > spend some time on it, but if the former, then I'd rather not today! > > > > On Mon, Jan 10, 2011 at 8:32 AM, Reinier Battenberg > > > > <[email protected]> wrote: > > > the .14 also works over TEAMS. The problem is with the whole subnet, > > > on SEACOM i can not even resolve names (like mctim, are you on the > > > same upstream?) > > > > the upstream of my provider is TATA. > > > > because 209.88.90.14 is the DNS server for this domain, too. > > > > > > there is no reverse DNS for this subnet. That is one issue: > > > > C:\Documents and Settings\Administrator>dig @ns.gta.gov.zw. > > 90.88.209.in-addr.ar pa > > > > ; <<>> DiG 9.3.2 <<>> @ns.gta.gov.zw. 90.88.209.in-addr.arpa > > ; (1 server found) > > ;; global options: printcmd > > ;; Got answer: > > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 742 > > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 > > > > ;; QUESTION SECTION: > > ;90.88.209.in-addr.arpa. IN A > > > > ;; AUTHORITY SECTION: > > 90.88.209.in-addr.arpa. 86400 IN SOA gta.gov.zw. > > webmaster.gta.gov.zw . 2006101301 28800 14400 3600000 86400 > > > > ;; Query time: 1078 msec > > ;; SERVER: 209.88.90.3#53(209.88.90.3) > > ;; WHEN: Mon Jan 10 08:51:00 2011 > > ;; MSG SIZE rcvd: 96 > > > > > r...@devispconf:~# ping 209.88.90.14 > > > > > > PING 209.88.90.14 (209.88.90.14) 56(84) bytes of data. > > > > > > 64 bytes from 209.88.90.14: icmp_seq=1 ttl=45 time=789 ms > > > > > > 64 bytes from 209.88.90.14: icmp_seq=2 ttl=45 time=788 ms > > > > > > --- 209.88.90.14 ping statistics --- > > > > I get SFA when I ping that IP: > > > > C:\Documents and Settings\Administrator>ping 209.88.90.14 > > > > Pinging 209.88.90.14 with 32 bytes of data: > > > > Request timed out. > > Request timed out. > > Request timed out. > > Request timed out. > > > > Ping statistics for 209.88.90.14: > > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), > > > > but as you can see, I can not resolve the IP from the hostname: > > > ping gta.gov.zw > > > > Ping request could not find host gta.gov.zw. Please check the name and > > try again > > > > so it is a DNS issue, as well, perhaps as a connectivity issue. > > > > I cannot, unlike Hari, use 8.8.8.8 to get an answer from dig: > > > > C:\Documents and Settings\Administrator>dig @8.8.8.8 gta.gov.zw > > > > ; <<>> DiG 9.3.2 <<>> @8.8.8.8 gta.gov.zw > > ; (1 server found) > > ;; global options: printcmd > > ;; Got answer: > > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 635 > > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 > > > > ;; QUESTION SECTION: > > ;gta.gov.zw. IN A > > > > ;; AUTHORITY SECTION: > > gta.gov.zw. 1800 IN SOA > > ns.gta.gov.zw. > > webmaster.gta.gov .zw. 2010072000 28800 14400 360000 86400 > > > > ;; Query time: 1046 msec > > ;; SERVER: 8.8.8.8#53(8.8.8.8) > > ;; WHEN: Mon Jan 10 08:44:10 2011 > > ;; MSG SIZE rcvd: 77 > > > > > > Nor can I get an answer from the ns that has the SOA: > > > > C:\Documents and Settings\Administrator>dig @ns.gta.gov.zw. gta.gov.zw > > > > ; <<>> DiG 9.3.2 <<>> @ns.gta.gov.zw. gta.gov.zw > > ; (1 server found) > > ;; global options: printcmd > > ;; Got answer: > > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 346 > > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 > > > > ;; QUESTION SECTION: > > ;gta.gov.zw. IN A > > > > ;; AUTHORITY SECTION: > > gta.gov.zw. 86400 IN SOA > > ns.gta.gov.zw. > > webmaster.gta.gov .zw. 2010110900 28800 14400 360000 86400 > > > > ;; Query time: 906 msec > > ;; SERVER: 209.88.90.3#53(209.88.90.3) > > ;; WHEN: Mon Jan 10 08:44:43 2011 > > ;; MSG SIZE rcvd: 77 > > > > > 3 packets transmitted, 2 received, 33% packet loss, time 2004ms > > > > > > rtt min/avg/max/mdev = 788.927/789.188/789.450/0.926 ms > > > > > > r...@devispconf:~# telnet 209.88.90.14 80 > > > > > > Trying 209.88.90.14... > > > > > > Connected to 209.88.90.14. > > > > So you CAN connect (for some value of that word) to that address? > > > > > Escape character is '^]'. > > > > > > ^] > > > > > > telnet> > > > > > > So, with my ISP and SEACOM > > > > It looks like SEACOM isn't at all involved in the L3 issues on this > > one. > > > > > > not being helpful, who di I contact? > > > > [email protected], that is in the dig result. > > > > and from robtex: > > > > contact information for gta.gov.zw > > [email protected] (responsible for gta.gov.zw) > > [email protected] (responsible for gip.net) > > [email protected] (responsible for telone.co.zw) > > [email protected] (responsible for co.zw) > > > > > > telone is their upstream AFAICS. > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > _______________________________________________ The Uganda Linux User Group: http://linux.or.ug Send messages to this mailing list by addressing e-mails to: [email protected] Mailing list archives: http://www.mail-archive.com/[email protected]/ Mailing list settings: http://kym.net/mailman/listinfo/lug To unsubscribe: http://kym.net/mailman/options/lug The Uganda LUG mailing list is generously hosted by INFOCOM: http://www.infocom.co.ug/ The above comments and data are owned by whoever posted them (including attachments if any). The mailing list host is not responsible for them in any way. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
