Thanks too everybody for there help. I still don't know what the problem
is. I now do know the query is only going to, two of the DNS servers. I
don't know why, everything looks good.
I did learn more and now have a couple good sites for helping.
thanks again to everybody
david
--
redhat-l
This is a very good site. Thanks for pointing it out.
I would like to give out the domain, but can't and keep my job. Sorry
about that.
Below is what I got back from the website
In answer to your question the three servers are listed:
DomainTypeClassTTLAnswer
domain.com.NS IN
On Tue, 2003-09-30 at 13:09, 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 se
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 curr
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?
david
On Tue, 30 Sep 2003,
This has to do with how long you primary and secondary dns servers have
been down. Since most dns servers operate a cache it will take awhile
for all the correct settings to propagate around the ether world. If
they have been down for more than a couple of days I would say your dns
server isn't p
