Search Again: recursion problem? From: Cayce Will Date: Monday, April 12, 2004 Time: 9:55:32 am Hello, A customer of mine is having a IP lookup problem and I can't quite pin point what is going on. We are running QuickDNS 2.2.4. Problem: Customer's IP address periodically fails to resolve. Situation: Customer has Charter for cable modem access. His IP address is 24.231.175.38. Customer has email account and web site hosted with us at www.rjdives.com. When his IP fails to resolve his pop client times out and he also apparently can't connect via FTP but I'm not sure how DNS problems would screw that up. So far, I've verified that http://remote.12dt.com/rns/ also fails to resolve his address when the problem pops up, but at the same time, http://www.dnsstuff.com/tools/ptr.ch?ip=24.231.175.38 works fine and resolves the IP. Dig produces: ; <<>> DiG 9.2.2 <<>> -x 24.231.175.38 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57358 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;38.175.231.24.in-addr.arpa. IN PTR ;; Query time: 32 msec ;; SERVER: 63.169.164.12#53(63.169.164.12) ;; WHEN: Mon Apr 12 12:49:31 2004 ;; MSG SIZE rcvd: 44 but tracing the dig produces ; <<>> DiG 9.2.2 <<>> +trace -x 24.231.175.38 ;; global options: printcmd . 216010 IN NS M.ROOT-SERVERS.NET. . 216010 IN NS I.ROOT-SERVERS.NET. . 216010 IN NS E.ROOT-SERVERS.NET. . 216010 IN NS D.ROOT-SERVERS.NET. . 216010 IN NS A.ROOT-SERVERS.NET. . 216010 IN NS H.ROOT-SERVERS.NET. . 216010 IN NS C.ROOT-SERVERS.NET. . 216010 IN NS G.ROOT-SERVERS.NET. . 216010 IN NS F.ROOT-SERVERS.NET. . 216010 IN NS B.ROOT-SERVERS.NET. . 216010 IN NS J.ROOT-SERVERS.NET. . 216010 IN NS K.ROOT-SERVERS.NET. . 216010 IN NS L.ROOT-SERVERS.NET. ;; Received 478 bytes from 63.169.164.12#53(63.169.164.12) in 67 ms 24.in-addr.arpa. 86400 IN NS chia.ARIN.NET. 24.in-addr.arpa. 86400 IN NS dill.ARIN.NET. 24.in-addr.arpa. 86400 IN NS henna.ARIN.NET. 24.in-addr.arpa. 86400 IN NS indigo.ARIN.NET. 24.in-addr.arpa. 86400 IN NS epazote.ARIN.NET. 24.in-addr.arpa. 86400 IN NS figwort.ARIN.NET. 24.in-addr.arpa. 86400 IN NS ginseng.ARIN.NET. ;; Received 197 bytes from 202.12.27.33#53(M.ROOT-SERVERS.NET) in 241 ms 175.231.24.in-addr.arpa. 86400 IN NS ns0.charter.com. 175.231.24.in-addr.arpa. 86400 IN NS ns1.charter.com. 175.231.24.in-addr.arpa. 86400 IN NS ns2.charter.com. 175.231.24.in-addr.arpa. 86400 IN NS ns4.charter.com. ;; Received 127 bytes from 192.5.6.32#53(chia.ARIN.NET) in 96 ms 38.175.231.24.in-addr.arpa. 83104 IN PTR 24.231.175.38.bay.mi.chartermi.net. 175.231.24.in-addr.arpa. 83104 IN NS ns1.chartermi.net. 175.231.24.in-addr.arpa. 83104 IN NS ns2.chartermi.net. 175.231.24.in-addr.arpa. 83104 IN NS ns3.chartermi.net. 175.231.24.in-addr.arpa. 83104 IN NS ns4.chartermi.net. ;; Received 196 bytes from 24.196.241.10#53(ns0.charter.com) in 87 ms Can anyone see what the problem is? Is there a recursion setting in my version of QuickDNS? This problem only crept up about 4 weeks ago (maybe 5). Thanks for your time, Cayce ---- Cayce C. Will Systems Administrator DeepNet Communications, LLC www.deepnet.com

Messages In This Thread: recursion problem? by Cayce Will on Apr 12, 2004 at 9:55:32 am Re: recursion problem? by Men & Mice Support on Apr 12, 2004 at 10:26:00 am