Ok, I wasn't getting the IPs in my resolv.conf because I had
dhclient.conf modified to supersede to the local DNS. Here's what I
did to determine the DNS that my ISP was assigning me.
I changed the dhclient.conf back to empty and restarted the network.
This then put the IPs of the two DNS servers
Ah, yes..dig. Forgot that it had a resolve time in there.
Here's a perfect example of the slowness I'm talking about:
su-2.05b# dig yahoo.com
; <<>> DiG 8.3 <<>> yahoo.com
;; res options: init recurs defnam dnsrch
;; res_nsend: Operation timed out
su-2.05b# dig yahoo.com
; <<>> DiG 8.3 <<>> yah
The problem with resolv.conf is that it just puts insightbb.com in
there. Doing a whois on insightbb.com gives a few DNS servers but none
of them are any speedier lookups then the others. If I put the IP that
insightbb.com resolves to it's still slow.
On Sun, 2 Jan 2005 09:41:20 -0600, Josh Paetz
On Sunday 02 January 2005 09:22, David Daugherty wrote:
> I'm running BIND 9 for my own DNS and I'm connecting to the
> Internet through cable modem. In my named.conf I have a forwarders
> section where I put the IPs for my ISPs DNS. Since my connection to
> the ISP is DHCP how can I determine the
David Daugherty wrote:
Are there tools/commands I can use to determine the resolution time
that my lookups are taking? A lot of my web browser requests are
timing out (name lookups) and I have to keep hitting refresh until it
finally resolves.
I'd try using dig:
> dig www.freebsd.org
At the end loo
I'm running BIND 9 for my own DNS and I'm connecting to the Internet
through cable modem. In my named.conf I have a forwarders section
where I put the IPs for my ISPs DNS. Since my connection to the ISP is
DHCP how can I determine the DNS IPs that have been assigned? I don't
see it when man'ing ifc
