Sounds like a registration issue. Since as you say it is possible to perform dns requests directly to the working server a la "dig @server request" it seems like this third server has no NS record registered for your domain.
Suggest you have a look at www.dnsstuff.com (which, by the way, is currently resolving to 69.2.200.183). Their DNS Lookup tool will show you exactly how your DNS requests are being handled and referred. Or try this: http://www.dnsstuff.com/tools/lookup.ch?name=domain.to.query.com Look at the "Type" column in the table for the NS records; I bet your third, working nameserver isn't listed there.... Pete On Tue, Sep 30, 2003 at 02:09:36PM -0400, dbrett wrote: > The computers in the domain were all up. So even if the entries were > cached shouldn't the requests still work. (I thought the zone entries were > cached not the DNS) > > I though with the first two servers down, the request would go to the > third server. What am I missing? -- Pete Nuwayser <[EMAIL PROTECTED]> Federal Trade Commission Internet Lab Systems Administrator Bureau of Consumer Protection PGP 0x672DA1ED Washington, DC 20580 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
