Re: [opensuse] dns too slow?



On Fri, Feb 26, 2010 at 2:48 AM, Leen de Braal <ldb@xxxxxxxx> wrote:
Hi all,

Having some troubles with dns. Sometimes when sending mail it is not
possible to resolve the addressee's domain. When checking manualy with
dig, the domain will be shown. I have been checking this, when trying
another domain (from which I am quite sure it will not be cached) I can
see that the MX record is not resolved by the local server. When checking
again, it gives the right answer.
Could this be some time-out that is set too short, and is there a way to
make it wait a little longer, or check the second nameserver in
resolv.conf (which is the one from the ISP) before the time-out?

Config as follows:
- openSUSE 11.2 does routing, firewall, and named.
- openSUSE 11.1 does mail, and checks the nameserver on 11.2.

I have seen this happen, with DNS queries, when I fire up workstations
(including the server hosting named) the first thing in the morning.
I do boot the server first and when it comes online, I boot the
workstations.
The DLink DSL router chokes on too many simultaneous requests. I
know this for sure because ping requests to external hosts (via IP
numbers) also time out.

Everything settles down after a couple of minutes though.

I suggest you make sure that you do not have any network bottle necks,
before suspecting your internal DNS server. You can use tcdump,
wireshark etc. to monitor network traffic.

HTH
-- Arun Khan
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx



Relevant Pages

  • Re: blocking annoying login popup applets
    ... > DNS server as centralized within my local network? ... Another machine is definitely not necessary for a local caching DNS ... Choice of djbdns vs. BIND: ... domains will resolve to 192.168.27.1. ...
    (comp.os.linux.networking)
  • Re: DNS not authoritative for domain
    ... I am using an internal DHCP server which is also my DNS and WINS ... I have configured a PPTP VPN using ISA to test whether or not I had an issue ... >> I can correctly resolve short and FQDN inside my domain. ...
    (microsoft.public.windows.server.dns)
  • Re: Dns.GetHostEntry functionality
    ... server as well as a DNS server. ... It is only the device that cannot resolve the name. ... The router is connected to the cable modem to the internet, but the router has DHCP turned off. ... don't have a network server you normally will not have a DNS server. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: aol..
    ... These are all AOL's email server. ... DNS work fine. ... This newsgroup only focuses on SBS technical issues. ... If we unable to resolve this issue after steps above, ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2003 DNS not working using own ip address
    ... When it comes to DNS name resolution, ... the DNS server will respond to the ... client with a list of nearest names servers to resolve the name. ...
    (microsoft.public.windows.server.networking)