Slow internal resolution

Stewart.Ann Ann_Stewart at
Thu Mar 9 03:30:47 UTC 2000

One of our Web servers, which is, of course, outside the firewall, has a
name that doesn't end with our domain name.  Specifically, our domain is, our main Web site is <> ,
and the server in question (on the same subnet as
<> ) is called
<> .  The resolver lives at a different
agency;  we have nothing to do with it.  The resolver lives here
and I'm the homeless schizophrenic they picked up off the street to
administer it, so I only know rudimentary things about DNS and BIND.  To
make it worse, we're running BIND 4.9.3 and our cache table hasn't been
updated for 4.5 years. <>  has 2
aliases: and   All 3 are in our basic database,
which we call (I inherited all of this -- don't blame anything on
me).  The one in the subnet database file for 209.210.72 is
<>  (with a dot after it). As far as I can tell,
everything is right for <>  in our
DNS tables.  If you do an nslookup, the name gets changed to <> , and it
resolves to the correct IP address (

More information about the bind-users mailing list