On Thu, 2010-07-01 at 09:22 -0700, JD wrote: Well, you want to get your local nameserver resolving internet IP addresses. Because, by the sound of things, it's not. Or get rid of it, and just use the ISP's nameservers. Or decrease the timeout period before the computer consults another name server. Your computer tries the first name server (listed in resolv.conf) to resolve an address, and when it doesn't an answer, it tries the next one, after a time out period. For the next name look up, it repeats that process (from the first nameserver, again). If that time out period is long, you're always going to have long delays. You can use the dig tool to test things out. See the man file for more details, but in a nutshell. Type the name you want to test after the command, followed by the nameserver you want to query, after an @ sign. e.g. dig example.com @127.0.0.1 Quite how to get nscd working, in the first place, I really don't know. I've never bothered with half-baked name serving, I run BIND. Looking at the nscd and nscd.conf man files. But I don't think you put 127.0.0.1 in as a nameserver, I think you stick with your ISP's name servers in the resolv.conf file. And play with the nsswitch.conf file to change /how/ name solving lookups are done, rather than where. To put caching somewhere into the equation. Look at the "hosts" line in that conf file. Mine has this in it: #hosts: db files nisplus nis dns hosts: files dns The uncommented line means that mine *first* looks in the /etc/hosts file, *then* does a DNS query. The commented line was the original. My guess would be that you need something else before dns, to make use of nscd, first. Unless, nscd puts data into the hosts file. In my case, I ignore the name servers provided by my ISP. Every ISP that I've used over the last 10 years (I think), has had problems. Some were just useless, including two of the biggest ISPs in the country. I run BIND, and it consults the top root servers like a real DNS server is supposed to do, when it doesn't already have an answer. And it caches the results, like it's supposed to (according to the TTL data in the original records). All the computers on my LAN use my nameserver. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.

On 07/01/2010 06:05 PM, Rick Stevens wrote: I edited /etc/nscd.conf and set positive-time-to-live 3600 and I was no longer able to restart nscd service. I commented that line out, and I was able to restart it. You mean /etc/modprobe.d/blacklist.conf OK. I did that. But that was not the issue that was causing me any problems with nscd. My /etc/sysconfig/networking/devices/ifcfg-ra0 already has: IPV6INIT=no

On 07/01/2010 10:42 AM, Tom Horsley wrote: bind is too complex to run and maintain. Really, it is a huge overkill for what I need. I hope nscd authors will fix it soon so it does not purge it's cache every few seconds. I check'ed it's config file and the restart-interval 3600 seems reasonable.

On 07/01/2010 09:47 AM, JD wrote: How do I even find out that ipv6 is enabled?

Unfortunately, enabling or disabling IPV6 doesn't seem to have much to do with the library doing V6 DNS lookups. I could swear there was something added to nsswitch.conf or resolv.conf that you could set to disable v6 dns requests, but I can't remember what it was called. I run bind as a caching nameserver, forwarding lookups to my ISP's server and set the -4 option on the command line to make it stick to ipv4 and all my DNS lookup problems vanished.