some dns cannot solve domain

[Kevin Darcy]

Your "negative caching TTL" for the cedrat.com domain (the last value in
the SOA record) is set to 2 days, so some servers may have "remembered" the
non-existence of the cedrat.com A record for that amount of time. You might
want to consider lowering that value.

ns.wanadoo.fr is now resolving cedrat.com fine, and the TTL on the record
in its responses implies that it has been doing so since about 15 hours ago
(about 6:30am EST Monday).


-Kevin

Robert.Grasso at cedrat.com wrote:

> Hello,
>
> I am having a strange trouble. I am a part-time admin, so I don't know
> everything :-( I am managing our domain (cedrat.com), using BIND 9.2 on
> Mandrake 8.1; I recently learned how to set an IP to the domain string :
> in
> the SOA record, I set an A record telling :
> @                                 IN    SOA ....
>                                     IN   A  192.93.7.101
>
> the aim is that people can connect on our Web site NOT typing the first
> www.
>
> It seemed it worked. Well, SOME DNS are not able to solve the domain
> "cedrat.com" such as ns.wanadoo.fr, while other ones (such as
> imag.imag.fr) ARE
> able to solve it. More, ns.wanadoo.fr is ABLE to solve another domain
> called
> "flux.com". So I must have some misconfiguration : can sombedoy help ?
>
> Best regards
>
> Robert Grasso