Some lookups work, wome don;t

Barry Margolin barmar at bbnplanet.com
Sun Jan 30 04:02:03 UTC 2000


In article <38938254.B4E9B631 at home.com>, GK  <gknopp at home.com> wrote:
>Quick question.  New to this DNS stuff.  I have a DNS server running.  I
>can get to my web site www.calgarywebsite.com from some ISP's but not
>others.  For example, from work, I can get to the website no problem.
>The name is resolved.  But if I try from one of my dialup accounts, it
>can't seem to resolve the name?  Why would that be.

I don't see any obvious problems.

>What causes a client to goto the secondary DNS server?  Currently my
>secondary dns server is dead.  Is that the cause?  There is no traffic
>at this website.  I would assume that they would all hit the primary DNS
>server.  I think I must have something configured wrong.

Clients don't know which server is primary and which is secondary.  They
initially try them in an arbitrary order; if the first one they try doesn't
respond, they then try the other.  Over time they learn which one responds
more quickly, and keep using that one.  Since your secondary server is
dead, they should learn quickly that they should only use the primary, so I
don't think this should be causing your problem.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.



More information about the bind-users mailing list