BIND: Lookup of CNAME records

789456123_at_gmx.de
Date: 03/19/04

  • Next message: ktulu_at_net2000.com.au: "port forwarding and ipfw rules"
    Date: Fri, 19 Mar 2004 02:54:37 +0100 (MET)
    To: freebsd-net@freebsd.org
    
    

    I have set up a FreeBSD (5.2.1-RELEASE) box acting as a gateway and
    running version 8.3.7-REL of BIND. For testing purposes my
    configuration file looks as follows:

    options {
      directory "/etc/namedb";
      pid-file "/var/run/named/pid";

      forward only;

      forwarders {
        195.62.99.42;
        195.62.97.177;
      };

      query-source address * port 53;
    };

    zone "." {
      type hint;
      file "named.root";
    };

    This setup (actually a replacement for just adding the two nameservers
    to resolv.conf) works fine with lookup tools like "host", "nslookup",
    or "dnsquery". However, when I try to telnet or ftp a server whose
    name is a CNAME record, it takes about 77 seconds until the lookup is
    complete. This appears quite odd to me, as "host" does the lookup
    perfectly well and fast. Connections to A name records are no problem
    however.

    My first assumption was that "ftp" or "telnet" were not doing lookups
    properly. But modifying resolv.conf in a way that it uses the two
    nameservers directly (instead of the local nameserver) solved the
    CNAME lookup problem.

    What makes the whole story even more obscure: Lookups of clients on
    the LAN (they use the FreeBSD box as their nameserver) do work with A
    records as well as with CNAME records. Even when the lookup is
    initiated by some ftp or telnet client.

    My firewall is widely opened, for everything in and everything out.
    An upgrade to BIND-8.4.4 did not resolve my problem.

    I suppose the answer is quite simple, but I don't really see it at the
    moment, I'm afraid...

    Any help is greatly appreciated,
    Lutz

    -- 
    +++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++
    100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
    

  • Next message: ktulu_at_net2000.com.au: "port forwarding and ipfw rules"

    Relevant Pages

    • BIND: Lookup of CNAME records
      ... This setup (actually a replacement for just adding the two nameservers ... to resolv.conf) works fine with lookup tools like "host", "nslookup", ... name is a CNAME record, it takes about 77 seconds until the lookup is ... the LAN (they use the FreeBSD box as their nameserver) do work with A ...
      (comp.unix.bsd.freebsd.misc)
    • FreeBSD Security Advisory FreeBSD-SA-05:13.ipfw
      ... For general information regarding FreeBSD Security Advisories, ... including descriptions of the fields above, security branches, and the ... ipfwis a system facility which allows IP packet filtering, ... The ipfw tables lookup code caches the result of the last query. ...
      (Bugtraq)
    • FreeBSD Security Advisory FreeBSD-SA-05:13.ipfw
      ... For general information regarding FreeBSD Security Advisories, ... including descriptions of the fields above, security branches, and the ... ipfwis a system facility which allows IP packet filtering, ... The ipfw tables lookup code caches the result of the last query. ...
      (FreeBSD-Security)
    • [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-05:13.ipfw
      ... For general information regarding FreeBSD Security Advisories, ... including descriptions of the fields above, security branches, and the ... ipfwis a system facility which allows IP packet filtering, ... The ipfw tables lookup code caches the result of the last query. ...
      (freebsd-announce)
    • 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)