Re: Some servvices on my edge box slow to reply

From: clvrmnky (clvrmnky-uunet_at_coldmail.com.invalid)
Date: 09/22/04

  • Next message: Dave Uhring: "Re: Some servvices on my edge box slow to reply"
    Date: Tue, 21 Sep 2004 18:38:51 -0400
    
    

    On 21/09/2004 5:38 PM, Dave Uhring wrote:

    > On Tue, 21 Sep 2004 16:47:32 -0400, clvrmnky wrote:
    >
    >
    >>[...]
    >>clvrmnky@martini:~ # time nslookup 10.0.0.10
    >>Server: localhost
    >>Address: 127.0.0.1
    >>
    >>*** localhost can't find 10.0.0.10: Server failed
    >>
    >>real 1m11.335s
    >>user 0m0.000s
    >>sys 0m0.016s
    >>clvrmnky@martini:~ #
    >>clvrmnky@martini:~ # time host -a -v 10.0.0.10
    >>Query about 10.0.0.10 for record types ANY
    >>Finding reverse mapping for 10.0.0.10 ...
    >>Nameserver not responding
    >>10.0.0.10 ANY record not found, try again
    >
    >
    > If you are going to use DHCP for your hosts on your LAN and expect things
    > like ssh and ftp to work without delay then you really need to configure
    > dynamic DNS on the nameserver. It is not difficult to accomplish and if
    > you need a usable template, email me and I'll send you my /etc/dhcpd.conf
    > and /var/named/etc/named.conf files.
    >
    Ok. The problem is that this has worked a treat until today. I've had
    the same setup for years. I guess the lookups have just failed in a
    timely manner until now, but I'd like to know /why/. And why only on
    some virtual Apache instances? Why IMAP all of a sudden?

    >
    >>real 0m48.151s
    >>user 0m0.031s
    >>sys 0m0.008s
    >>clvrmnky@martini:~ #
    >>clvrmnky@martini:~ # time nslookup 10.0.0.254
    >>Server: localhost
    >>Address: 127.0.0.1
    >>
    >>*** localhost can't find 10.0.0.254: Server failed
    >
    >
    > If martini's IP address is .254 you have some serious problems in your
    > zone records. Do you even have an inverse lookup record file?
    >
    Really? What else would it be? 10.0.0.254 is a valid static address
    within 10.0.0 that I've given to the internal NIC. The resolver knows
    about it via /etc/hosts. I've never needed to do a reverse lookup on it
    before.

    I have a caching-only nameserver, so I've done nothing extra other than
    enabling that. I did the bare necessities out of the O'Reilly TCP/IP
    book and the OBSD FAQs to get a cashing nameserver working, and have
    never touched it since then.

    > You might consider upgrading your installation to 3.5 since your version
    > is no longer being supported with patches. In addition 3.5 has
    > BIND-9.2.3, which has fewer bugs and is more secure.

    I'm building new box to replace this one, which will be at 3.5.


  • Next message: Dave Uhring: "Re: Some servvices on my edge box slow to reply"

    Relevant Pages

    • Re: BIND: Lookup of CNAME records
      ... > name is a CNAME record, it takes about 77 seconds until the lookup is ... > nameservers directly solved the ... > CNAME lookup problem. ... for a simple caching DNS server setup (as ...
      (comp.unix.bsd.freebsd.misc)
    • Re: damn red xs again
      ... you can do to investigate the symptom as a problem with your DNS. ... switch to using the domain's nameserver. ... the normal lookup works without such symptoms. ... counters.honesty.com internet address = 209.11.131.36 ...
      (microsoft.public.windows.inetexplorer.ie6.browser)
    • Re: looking up???
      ... > That means i it lookup up the IP to connect to by resolving this name as ... > nameserver you configured your system for. ... substitute one of the worldwide DNS servers here. ... the delay is in the DNS lookup. ...
      (comp.os.linux.networking)
    • Re: SOLVED -- Re: Problems with a BIND server
      ... Likewise a client that uses it directly as its nameserver, ... If you look at that TCPDUMP use see the first lookup of say, ... The cache is 'ruined?' ... records in the parent zone, which is why the cache is "ruined". ...
      (comp.protocols.dns.bind)
    • Re: Mozilla and long time in resolving Hostnames
      ... I've tried the last version of Mozilla ... installed via Ports updated with CVSUP, ... lookup against 80.20.6.36: ... > Note that the nameserver of 212.216.112.112 responds ...
      (freebsd-questions)