On 2006, Oct 6, at 04:02, Wojciech Puchar wrote:
one of my users reporting problem sending e-mail to @mil.be
sendmail reports host name lookup failure
host reports
[EMAIL PROTECTED] ~]$ host -t mx mil.be
mil.be mail is handled by 10 hermes01.mil.be.
[EMAIL PROTECTED] ~]$ host -t a
one of my users reporting problem sending e-mail to @mil.be
sendmail reports host name lookup failure
host reports
[EMAIL PROTECTED] ~]$ host -t mx mil.be
mil.be mail is handled by 10 hermes01.mil.be.
[EMAIL PROTECTED] ~]$ host -t a hermes01.mil.be
hermes01.mil.be has address 194.7.21.40
Wojciech Puchar [EMAIL PROTECTED] wrote:
one of my users reporting problem sending e-mail to @mil.be
sendmail reports host name lookup failure
host reports
[EMAIL PROTECTED] ~]$ host -t mx mil.be
mil.be mail is handled by 10 hermes01.mil.be.
[EMAIL PROTECTED] ~]$ host -t a
where's a problem? while hostr is able to get IP addresses but then
reports servfail?
I don't see that error when I try the same lookups.
host -t a hermes01.mil.be
hermes01.mil.be has address 194.7.21.40
hermes01.mil.be has address 193.191.219.40
I suspect the problem is in your resolver
Wojciech Puchar [EMAIL PROTECTED] wrote:
where's a problem? while hostr is able to get IP addresses but then
reports servfail?
I don't see that error when I try the same lookups.
host -t a hermes01.mil.be
hermes01.mil.be has address 194.7.21.40
hermes01.mil.be has address
zone 0.0.127.in-addr.arpa in { type master; file 127;};
and then master and slaves domains definitions below.
Just a theory: Do you possibly have recursive queries locked down too
where is it set?
far, and does resolution of that name require recursion?
it is possible almost sure.