From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1ab93414cce31874699fbae8495257e0@proxima.alt.za> To: 9fans@cse.psu.edu Subject: Re: [9fans] stubbing Date: Wed, 12 Oct 2005 21:11:49 +0200 From: lucio@proxima.alt.za In-Reply-To: <4349587F.8070200@village.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 9a08c578-ead0-11e9-9d60-3106f5b1d025 > Thanks for taking the trouble to let me know about this. Perhaps now > that this message is going to you the jailer will accept you as a > legitimate visitor! Sorry to use the list for this, but Wes is otherwise unreacheable to me. Wes, here's another one for Bill, from a different host, albeit on the same physical wire as 192.96.32.135 (can't be helped, yet): > The original message was received at Tue, 11 Oct 2005 22:41:20 +0200 (SAST) > from lucio@localhost > > ----- The following addresses had transient non-fatal errors ----- > bilsch@village.com > wes@village.com > > ----- Transcript of session follows ----- > ... while talking to mail.village.com.: > >>> RCPT To: > <<< 450 Client host rejected: cannot find your hostname, [196.30.44.140] > wes@village.com... Deferred: 450 Client host rejected: cannot find your hostname, [196.30.44.140] > >>> RCPT To: > <<< 450 Client host rejected: cannot find your hostname, [196.30.44.140] > bilsch@village.com... Deferred: 450 Client host rejected: cannot find your hostname, [196.30.44.140] > Warning: message still undelivered after 4 hours > Will keep trying until message is 1 day old > I'd like to suggest two possible approaches to identify the problem: this is what the SOA for 32.96.192.in-addr.arpa ought to be, Bill may be able to determine where his DNS is failing by comparing results: 32.96.192.in-addr.arpa origin = ns.proxima.alt.za mail addr = lucio.proxima.alt.za serial = 2005082301 refresh = 10800 (3H) retry = 1800 (30M) expire = 3600000 (5w6d16h) minimum ttl = 86400 (1D) and for 44.30.196.in-addr.arpa is 44.30.196.in-addr.arpa origin = proxy.iba.co.za mail addr = lucio.proxima.alt.za serial = 2005092301 refresh = 10800 (3H) retry = 1800 (30M) expire = 3600000 (5w6d16h) minimum ttl = 86400 (1D) If Bill can't find these RRs, then he must work his way up the hierarchy until he determines where the gap is. Maybe I can save him some effort: myrtle:161$ nslookup -q=soa 30.196.in-addr.arpa Server: localhost Address: 127.0.0.1 Non-authoritative answer: 30.196.in-addr.arpa origin = ns1.iafrica.com mail addr = dns-admin.uunet.co.za serial = 2005101202 refresh = 43200 (12H) retry = 3600 (1H) expire = 2592000 (4w2d) minimum ttl = 86400 (1D) Authoritative answers can be found from: 30.196.in-addr.arpa nameserver = ns1.iafrica.com 30.196.in-addr.arpa nameserver = ns2.iafrica.com 30.196.in-addr.arpa nameserver = auth200.ns.uu.net 30.196.in-addr.arpa nameserver = auth210.ns.uu.net ns1.iafrica.com internet address = 196.7.0.139 ns2.iafrica.com internet address = 196.7.142.133 auth200.ns.uu.net internet address = 195.129.12.82 auth210.ns.uu.net internet address = 195.129.12.74 myrtle:162$ nslookup -q=soa 196.in-addr.arpa Server: localhost Address: 127.0.0.1 Non-authoritative answer: 196.in-addr.arpa origin = chia.arin.net mail addr = bind.arin.net serial = 2005101214 refresh = 1800 (30M) retry = 900 (15M) expire = 691200 (1w1d) minimum ttl = 10800 (3H) Authoritative answers can be found from: 196.in-addr.arpa nameserver = basil.arin.net 196.in-addr.arpa nameserver = henna.arin.net 196.in-addr.arpa nameserver = indigo.arin.net 196.in-addr.arpa nameserver = epazote.arin.net 196.in-addr.arpa nameserver = figwort.arin.net 196.in-addr.arpa nameserver = chia.arin.net 196.in-addr.arpa nameserver = dill.arin.net basil.arin.net internet address = 192.55.83.32 henna.arin.net internet address = 192.26.92.32 indigo.arin.net internet address = 192.31.80.32 epazote.arin.net internet address = 192.41.162.32 figwort.arin.net internet address = 192.42.93.32 chia.arin.net IPv6 address = 2001:440:2000:1::21 chia.arin.net internet address = 192.5.6.32 dill.arin.net internet address = 192.35.51.32 The above ought to suffice for the one IP, the other gives: myrtle:164$ nslookup -q=soa 96.192.in-addr.arpa Server: localhost Address: 127.0.0.1 Non-authoritative answer: 96.192.in-addr.arpa origin = disa.tenet.ac.za mail addr = eosap.tenet.ac.za serial = 200509220 refresh = 3600 (1H) retry = 3600 (1H) expire = 2592000 (4w2d) minimum ttl = 86400 (1D) Authoritative answers can be found from: 96.192.in-addr.arpa nameserver = ns1.afrinic.net 96.192.in-addr.arpa nameserver = disa.tenet.ac.za 96.192.in-addr.arpa nameserver = rain.psg.com 96.192.in-addr.arpa nameserver = ucthpx.uct.ac.za myrtle:163$ nslookup -q=soa 192.in-addr.arpa Server: localhost Address: 127.0.0.1 Non-authoritative answer: 192.in-addr.arpa origin = chia.arin.net mail addr = bind.arin.net serial = 2005101214 refresh = 1800 (30M) retry = 900 (15M) expire = 691200 (1w1d) minimum ttl = 10800 (3H) Authoritative answers can be found from: 192.in-addr.arpa nameserver = chia.arin.net 192.in-addr.arpa nameserver = dill.arin.net 192.in-addr.arpa nameserver = basil.arin.net 192.in-addr.arpa nameserver = henna.arin.net 192.in-addr.arpa nameserver = indigo.arin.net 192.in-addr.arpa nameserver = epazote.arin.net 192.in-addr.arpa nameserver = figwort.arin.net chia.arin.net IPv6 address = 2001:440:2000:1::21 chia.arin.net internet address = 192.5.6.32 dill.arin.net internet address = 192.35.51.32 basil.arin.net internet address = 192.55.83.32 henna.arin.net internet address = 192.26.92.32 indigo.arin.net internet address = 192.31.80.32 epazote.arin.net internet address = 192.41.162.32 figwort.arin.net internet address = 192.42.93.32 The other experiment would involve setting the DNS server on Bill's equipment to act as secondary for the two domains (44.30.196.in-addr.arpa and 32.96.192.in-addr.arpa) by fetching the zone files from their respective nameservers. I would have to grant access, but it may be worth doing to establish the circumstances that cause the failure by eliminating some unknowns. ++L