dnscache hung...

[George Georgalis]

On Sat, Jun 15, 2002 at 02:46:12PM -0700, John H. Robinson, IV wrote:
>On Sat, Jun 15, 2002 at 09:15:40AM -0400, George Georgalis wrote:
>> On Sat, Jun 15, 2002 at 01:33:03AM -0700, John H. Robinson, IV wrote:
>> >On Fri, Jun 14, 2002 at 04:36:45PM -0400, George Georgalis wrote:
>> >> I have a tinydns/dnscache server running, well sort of.
>> >
>> >tinydns is what you tell your domain registrar your nameserver is.
>> >dnscache is what you you put in /etc/resolv.conf
>> >
>> >since both utilise UDP port 53, they both can't/won't be bound to the
>> >same IP address.
>> 
>> Yes, dnscache is listening on a LAN ip and also in resolv.conf, while
>> tinydns is listening on 127.53.0.1.
>> 
>> [root at host root]# netstat -ptuna | grep 53 
>> tcp        0      0 192.168.33.44:53        0.0.0.0:*               LISTEN      22078/dnscache      
>> udp        0      0 192.168.33.44:53        0.0.0.0:*                           22078/dnscache      
>> udp        0      0 127.53.0.1:53           0.0.0.0:*                           1133/tinydns        
>
>ah!  very good.    if you have no one trying to get at 127.53.0.1 to try
>to resolve any of your domain names, of course (except your
>local/external dnscache of course)
>
>it ``hung'' when doing only one query, meaning that other queries still
>got through, correct?  if that is the case, that is telling me that
>dnscache is trying to get ahold of a nameserver, but can't for whatever
>reason (unroutable, host not reposponding, no one listening at the
>report port, various firewall issues, etc)

no, it made about 10 connections and didn't answer anything but what was
in tinydns.

>dnscache by default looks to the root servers to resolve things. the
>IP's of the root servers is kept in /service/dnscache/root/servers/@
>if you add a file to root/servers (say, 23.168.192.in-addr.arpa) with an
>IP address of a resolver (tinydns) that is authoritative for that
>domain, then dnscache will query that instead of the root servers.
>
>in this case, a 
>echo 127.53.0.1 > root/servers/galis.org
>may be in order.
>
>if they _all_ hung, then that is indicative of even bigger problems.

You mean the ISP? No route to root servers? (I _was_ logged in remotely)

[root at host root]# ls /service/dnscache/root/servers/
@  33.22.11.in-addr.arpa  168.192.in-addr.arpa  example.com  local

// George


-- 
GEORGE GEORGALIS, System Admin/Architect    cell: 347-451-8229 
Security Services, Web, Mail,            mailto:george at galis.org 
File, Print, DB and DNS Servers.       http://www.galis.org/george