The problem is that here.com NS says ns1.psi.net and ns2.psi.net, but
those servers are failing to give any answer, even for an SOA..
the fix is to let InterNIC know about this imporoper delegation so they
can remove the invalid NS records.
On Wed, 7 Jul 1999, Peter Radcliffe wrote:
> One of my users is on a mailing list one which someone is sending mail
> with the from line 'From: me <me@???>' which doesn't seem to be
> valid (here.com has no A or MX records) but verification fails:
>
> DNS lookup of here.com (MX) gave TRY_AGAIN
> here.com in dns_again_means_nonexist? no (end of list)
> lookuphost router deferred here.com
> message: host lookup did not complete
> search_tidyup called
> me@??? cannot be resolved at this time:
> host lookup did not complete
>
> Now, presumably I can put here.com in dns_again_means_nonexist and
> it'll bounce these right away rather than accepting/rejecting but
> is this the only way to deal with domains that are continually
> broken like this ?
>
> P ... off to mail the tech contact for here.com
>
> --
> pir pir@??? pir@??? pir@???
>
>
> --
> *** Exim information can be found at http://www.exim.org/ ***
>
>
