Slow resolution

[jtnt]

I use my Xserve to provide DNS (among other things) to my office of roughly a dozen users.

Let’s say I go to domain-a.com for the first time, so it takes a couple seconds for DNS to get info on it and send me on my way. That is, there is an initial delay in loading the site.

I then go to that same URL, say, 10 minutes later. I get the same few second delay. It’s not waiting for the site to load, it’s an initial connection delay, precisely like the initial delay experienced the first time I go to the URL. This happens on all machines. (and if take my Xserve out of the DNS search list and just use my IPs, this delay does not happen – but this is why I use my Xserve for this, to speed this stuff up and take the round-trip to my ISP out of the way).

I would think that the DNS info for this site would be cached and it would be immediate. Does bind dump its memory of a URL after a few minutes of it not being accessed or anything like that?

Any help/tips/solutions/etc. are greatly appreciated.

[jtnt]

Did I not provide enough information or explain my problem well enough? Or was it just a silly question?

Just looking for some help if anybody has anything to offer.

TIA

[jtnt]

At the risk of sounding really stupid now, I’m not sure what you mean – or rather, how to answer your question.

[JasonHeiser]

I’m having the same issue with DNS running on on our G5 10.3.8 server. There’s a 3-4 second delay in resolving domain names not hosted on the box, and it’s irritating me terribly. Can the performance be tweaked?

[JasonHeiser]

I disliked feeling like a “Me too!” moron, so I dug in and learned a thing or two about BIND. My DNS resolutions go a lot faster now that I’m forwarding them to our ISP’s servers. You can do the same by adding a FORWARDERS option in your OPTIONS statement in /etc/named.conf.

options {
        directory "/var/named";
        recursion true;
        forwarders {209.46.63.1;209.46.63.6;};
        allow-transfer {none;};
};

[Author]

Posts