Re: BIND TIMEOUT - ReadList.com

2 msg	Loc records for entire network
4 msg	UDP port 1086
2 msg	forwarding parent and child to different servers
2 msg	Intergration of ADS with BIND
7 msg	DNS PTR Records subnet
9 msg	Name Resolve
2 msg	root Servers referral
3 msg	TSIG
7 msg	NAPTR issue with HPUX
2 msg	upgrade to 9.4.0 issues
3 msg	Dynamic update - journal file management
3 msg	bind9/dhcp3 DDNS error

BIND TIMEOUT
\ Andrea (9 Mar 2007)
. \ Andrea (9 Mar 2007)
. . \ Danny Mayer (10 Mar 2007)
. . \ Andrea (12 Mar 2007)
. . . \ Peter Dambier (12 Mar 2007)
. . . . \ Nick Allum (12 Mar 2007)
. \ Andrea (12 Mar 2007)
. . \ Nick Allum (12 Mar 2007)
. \ Mark Andrews (13 Mar 2007)

5 msg	Some Questions on BIND and IPv4 Anycast
2 msg	Misbehaviour with root-server priming queries
2 msg	Repeated queries to the root-servers
5 msg	About Zone refresh on a very big DNS server.
1 msg	building bind with mysql
2 msg	somewhat off-topic, but the ISC web-site ...
1 msg	Number of CPU detected by Bind 9.4.0

Subject:	Re: BIND TIMEOUT
Group:	Bind-users
From:	Mark Andrews
Date:	13 Mar 2007

> This is just with nslookup I presume as it has a short timeout. We run
> into this also if it is a newly visited site and you perform an nslookup
> for it for the first time we see the same time out.
>
> However if you perform a dig on a not previously visited site it will
> return an answer.
>
> Note that this would not be a problem for example in Internet Explorer
> or any other browser on a Windows desktop, this time out it only seen
> using nslookup on a domain not previously visited.

Please remember that Windows ships with a nslookup. You
need to take care to identify which nslookup you are using.

> -----Original Message-----
> From: bind-users-bounce [mailto:bind-users-bounce] On
> Behalf Of Andrea
> Sent: Monday, March 12, 2007 10:40 AM
> To: comp-protocols-dns-bind
> Subject: Re: BIND TIMEOUT
>
>
> Only the first time.
> subsequent attempts are OK.
> ...Ok until i' dont' restart DNS Service.
>
>
> "Nick Allum" <Nick.Allum> ha scritto nel messaggio
> news:et3je2$2gao$1...
> > Does this happen only on your first attempt to resolve a new external
> > domain.
> >
> > If you query something.com multiple times is it only on the first
> > attempt that it times out, and subsequent attempts are ok?
> >
> > -----Original Message-----
> > From: bind-users-bounce [mailto:bind-users-bounce] On
> > Behalf Of Peter Dambier
> > Sent: Monday, March 12, 2007 8:38 AM
> > To: Andrea
> > Cc: comp-protocols-dns-bind
> > Subject: Re: BIND TIMEOUT
> >
> >
> > Andrea wrote:
> >> hallo
> >> sorry, i speak English just a little...
> >>
> >> when i query (with nslookup) some site on my dns....it answer
> >> immediatly.
> >>
> >> When I query other site (example ripe.net) it answer (first query)
> >>
> >> DNS request timed out.
> >> timeout was 2 seconds.
> >>
> >> at the SECOND query on the same Site....it answer correctly.
> >>
> >> I think that if it can use "more time"....it can answer at the first
> >> query.
> >>
> >
> > I think the problem is your isp. Their open resolver is answering to
> > slowly. best get rid of them and use bind as a resolver.
> >
> > look into your named.conf and find lines with "forwarder" and make
> > them a comment. The line should look like "# forwarders ..." or "//
> > forwarders ..." now.
> >
> > be shure to have something like
> >
> > # zone "." in {
> > # type hint;
> > # file "root.hint";
> > # };
> >
> > I have made this a comment because I am using an italian root-server:
> >
> > zone "." in {
> > type slave;
> > file "cesidian-root.zone";
> > masters { 212.97.45.53; 82.199.205.254 port 3001; };
> > };
> >
> >
> > please be shure that nslookup is using bind and not you isp.
> >
> > Somewhere windows does get its dns servers "automatically via dhcp)"
> > or you can put in two nameservers manually. Here you must put in you
> > bind.
> >
> > The line
> >
> > masters { 212.97.45.53; 82.199.205.254 port 3001; };
> >
> > Tells bind to slave the root-zone from
> >
> > 212.97.45.53; from host 212.97.45.53 port 53, the normal dns port.
> >
> > 82.199.205.254 port 3001; or from host 212.97.45.53 port 3001.
> >
> > Nowadays isp are blocking port 53 and open resolvers. That is why we
> > had to move this one to another port.
> >
> > Open resolvers are attacked or used for attacking. That is why best
> > get rid of them and run you own.
> >
> >
> > Kind regards
> > Peter and Karin Dambier
> >
> >>
> >>
> >>
> >> "Danny Mayer" <mayer> ha scritto nel messaggio
> >> news:est5ct$2ajg$1...
> >>
> >>>Andrea wrote:
> >>>
> >>>>hello
> >>>>when i query my DNS...it always try to answer me in two seconds. Is
> >>>>possible to enlarge this measure to...10 seconds? I use Bind 9.4 on
> >>>>Windows. I can put "something" in boot.options? Thank you to all
> >>>
> >>>I'm not really sure what this question means. What is the real issue
> >>>that you are trying to resolve. Maybe looking at the symptoms of what
>
> >>>you are seeing will help us answer the question.
> >>>
> >>>Danny
> >>>
> >>>
> >>
> >>
> >
> >
> > --
> > Peter and Karin Dambier
> > Cesidian Root - Radice Cesidiana
> > Rimbacher-Strasse 16
> > D-69509 Moerlenbach-Bonsweiher
> > +49(6209)795-816 (Telekom)
> > +49(6252)750-308 (VoIP: sipgate.de)
> > mail: peter
> > mail: peter
> > http://iason.site.voila.fr/ https://sourceforge.net/projects/iason/
> > http://www.cesidianroot.com/
> >
> >
>
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews