recursion problem?

Re: recursion problem?

From:

Date:

Time:

The servers to which the reverse zone is delegated do not return
authoritative answers when asked about the zone. All four servers
have the answer in cache, though (and all four offer recursion to my
address, which is not in their network). It's unclear how they're
finding the zone, given that the delegation for the zone is entirely
lame.

It seems likely that once these answers expire from the caches of the
four servers, the PTR record will be unlocatable until and unless
someone sends one of these servers a recursive query about it. They
have some unusual ability to locate the answer, such as a specific
configuration telling them what servers to ask about this zone.

The result is an on-again, off-again ability for the rest of the
world to find this PTR record. Charter needs to fix this, and it's
not hard for them to do so - there are several possible solutions.

In the meantime, anyone using the BIND name server for recursion can
work around the problem. QuickDNS (when managing the BIND name
server) doesn't offer an interface for this setting, but the
following "forward" zone will work:

zone 175.231.24.in-addr.arpa. {
type forward;
forwarders {
24.213.60.77;
24.213.60.78;
24.247.24.38;
24.247.28.38; };
};

(You would put this in conf/user_after if using QuickDNS. Requires
QuickDNS 4.5 or later, as I recall - otherwise, QuickDNS Remote will
have a problem with this.)

There is no way to solve this using QuickDNS Pro 2.x or 3.x, nor (I
believe) QuickDNS managing a Microsoft DNS server.
____________________________________________________________________
Chris Buxton Men & Mice
Customer Support Specialist Making DNS Easy

At 12:54 PM -0400 4/12/04, Cayce Will wrote:
>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

Sales:
888/4-DPOINT

Support:
858/452-3696