On 15 October 2001, Paulo Henrique Baptista de Oliveira said:
> at server A I got exactly the same output than you
OK, good.
> and at server B I
> got the following strange error:
>
> internet:~# host -t MX telemar-rj.com.br
> telemar-rj.com.br MX 1 mailgwo01.telemar.com.br
> telemar-rj.com.br MX 0 mailgwi01.telemar.com.br
> internet:~# host mailgwo01.telemar.com.br
> mailgwo01.telemar.com.br does not exist, try again
> internet:~# host mailgwo01.telemar.com.br
> mailgwo01.telemar.com.br does not exist, try again
> internet:~# host mailgwi01.telemar.com.br
> mailgwi01.telemar.com.br does not exist, try again
Clearly a DNS problem on server B. If you're not the DNS admin at your
site, talk to that person. If you *are* the DNS admin at your site,
start learning!
The first place to look is /etc/resolv.conf on B. What nameservers is B
configured to consult? Try querying different nameservers from B. Use
a packet-tracer like ethereal to watch what's really going on between
DNS clients on B (like "host" or "exim") and B's nameserver(s).
Good luck --
Greg
--
Greg Ward - software developer gward@???
MEMS Exchange http://www.mems-exchange.org
