MX resolving problems

[Kevin Darcy]

There's only 1 non-lame server for abssys.com -- aurora.abssys.com -- and
it's not returning any Authority Section in its responses, which is rather
unusual although I think technically legal. If you're running BIND 8 with
its infamous "lack of query restart" this no-Authority behavior may,
however, result in your queries for that domain occasionally timing out.


- Kevin

Nico Lembrechts wrote:

> hello,
>
> Today we noticed that there where some mails for abssys.com in our
> (sendmail) queue. The problem was that the nslookup for this domain
> failed.
> I tried manually to do a nslookup for this domain and i found the ip,
> then i set type=mx and indeed the MX records where not found. So i tried
>
> another nameserver, this one resolved everything fine.
> Back on our nameserver i tried to resolve some other MX records for
> other domains, they all worked fine ???
>
> How is it possible that our nameserver can't resolve (only the MX
> records) for one specific domain while other servers could do the job.
>
> any ideas ?
>
> Thanx in advance
>
> Nico