On Tue, 2003-09-02 at 19:55, Marc Adler wrote: > * Jason Dixon <[EMAIL PROTECTED]> [2003-09-02 13:42]: > > On Tue, 2003-09-02 at 19:35, Marc Adler wrote: > > > * NfoCipher <[EMAIL PROTECTED]> [2003-09-02 12:59]: > > > > On Tue, 2003-09-02 at 17:42, Marc Adler wrote: > > > > > I took a look at /etc/resolv.conf and there were a few entries in it, > > > > > but how do I know if they are valid? > > > > > > > > > Well, your isp is sending those to you via dhcp, so you can assume > > > > they're valid but they may not respond very fast - causing a delay. > > > > You can try running your own caching dns server. > > > > /etc/rc.d/init.d/named start > > > > > > > > edit /etc/resolv.conf > > > > > ; generated by /sbin/dhclient-script > > > > search your.local.domain.here > > > > > > I'm not sure what my localdomain is - I've named my LAN kapakipika and > > > my two computers nui and iki (nui.kapakipika and iki.kapakipika), so > > > should I just enter kapakipika? Or kapakipika.hawaii.rr.com? I went > > > ahead and entered kapakipika by itself, and it seems to work, but would > > > it be better to enter kapakipika.hawaii.rr.com? > > > > > > > nameserver 127.0.0.1 > > > > > nameserver 24.25.227.32 > > > > > nameserver 24.25.227.34 > > > > > nameserver 24.25.227.36 > > > > I'm happy that your postfix is temporarily fixed, but I hope you > > reconsider running named to do it. It sounds like you're having DNS > > resolution problems with your provider. The commands I sent in my > > previous mail should give a better idea of the problem. Ideally, > > tcpdumps should be gathered to see what is causing the delays. > > Something like "tcpdump -ni eth0 port 53" should be very revealing. > > > > Ok. Your message came just a few seconds after I responded. I want to > try the commands you suggested. Should I just type time host yahoo.com > etc. at the command line? (Hey, why don't I just try it and find out?) > Ok. It hangs, but upon pressing ctrl-c, I get: > > [EMAIL PROTECTED] ~]$ time host yahoo.com 24.25.227.32 > > real 0m5.123s > user 0m0.010s > sys 0m0.000s
Yup, the nameserver listed first in your /etc/resolv.conf isn't returning DNS queries properly. I suspect this is a temporary problem. If I were you, I'd delete that line from your file, that's what's causing your delay. If dhcpd places that line back in, you can make changes to your network configuration to use only those other two nameservers, rather than gathering DNS information via DHCPOFFER. P.S. In the meantime, please disable your named. :) P.P.S. The command you ran above was a combination of the "time" command timing the execution of the other command "host ...". It measures how long it takes for the resolution to occur. The result of the first command was just the amount of time that expired when you hit CTRL-C. -- Jason Dixon, RHCE DixonGroup Consulting http://www.dixongroup.net -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
