Strange problem.

[Simon Waters]

Peter Magnusson wrote:
> 
> All .CX TLD DNS-servers worked
> and the information was right, but the DNS-server that was used on that
> computer still refused to know anything about the NS records for
> flashdance.cx. 

DOC has a bit of a fit - 7 errors omitted - looking for
flashdance.cx.

The ultradns name servers for domain CX don't appear to be
providing glue for the the ns{1,2,3}.flashdance.cx name servers,
this could explain your problems.

The guessable SLD domains for CX all use 'out of bailiwick'
nameservers (gov.cx, ac.cx etc) which I guess tells us a little
more than that they aren't going to see this problem.

The SOA for CX returned indicates that the zones are uptodate so
this probably won't fix itself.

> ALL this started just some months ago, before that everything worked just
> fine. First i thought that it was something wrong with bind 9.2.1 so
> i downgraded to 9.2.0 but that didnt help either.

There probably is something wrong with 9.2.1 but I doubt this is
it.

 With apologies to those copied if I'm completely wrong, but I
figured you'd want to know sooner than later.

 Simon