HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

hp tcpip - smtp mx_record error

 
adarsh_4
Frequent Advisor

hp tcpip - smtp mx_record error

i was able to send vms mail to our exchange server before but it has stopped working after a upgrade of our exchange server.

I get the following error when i do a " sh mx_record hostname"

TCPIP> sh mx exchsvr1.fsc.com.fj
getmxrr: name = EXCHSVR1.FSC.COM.FJ

getmxrr: res_search() failed
TCPIP$GET_MX: getmxrr() failed

please advise what could be wrong. thank you

4 REPLIES
Steven Schweda
Honored Contributor

Re: hp tcpip - smtp mx_record error

> hp tcpip [...]

Not so informative as output from:
tcpip show version

> [...] but it has stopped working after a
> upgrade of our exchange server.

Does it work for any other server?

> TCPIP> sh mx exchsvr1.fsc.com.fj

How about plain "show host ..."? Is this
thing in the DNS data now?

tcpip show name_service
adarsh_4
Frequent Advisor

Re: hp tcpip - smtp mx_record error

TCPIP> show version

HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 6
on a COMPAQ AlphaServer DS20E 666 MHz running OpenVMS V7.3-2

#########################################

>Does it work for any other server?

yes,this is working from the other server.

#############################################

TCPIP> show name_service

BIND Resolver Parameters

Local domain: fsc.com.fj

System

State: Started, Enabled

Transport: UDP
Domain: FSC.COM.FJ
Retry: 4
Timeout: 4
Servers: DC.FSC.COM.FJ
Path: FSC.COM.FJ, COM.FJ

Process

State: Enabled

Transport:
Domain:
Retry:
Timeout:
Servers:
Path:


hope this is helpful
Jeremy Begg
Trusted Contributor

Re: hp tcpip - smtp mx_record error

The getmxerr message might mean there is no such MX record. Try this:

$ mcr tcpip$nslookup -q=mx exchsvr1.fsc.com.fj

and see what you get.

If 'exchsvr1.fsc.com.fj' is the Exchange server you shouldn't need to use an MX record anyway. I would think the more likely setup is that there is an MX record for 'fsc.com.fj' which returns the hostname 'exchsvr1.fsc.com.fj'.

Regards,
Jeremy Begg
Steven Schweda
Honored Contributor

Re: hp tcpip - smtp mx_record error

> > TCPIP> sh mx exchsvr1.fsc.com.fj
>
> How about plain "show host ..."? Is this
> thing in the DNS data now?

Still wondering. From here:

alp $ nslookup exchsvr1.fsc.com.fj
Server: alp-l.antinode.info
Address: 10.0.0.9

*** alp-l.antinode.info can't find exchsvr1.fsc.com.fj: Non-existent host/domain

alp $ nslookup DC.FSC.COM.FJ
Server: alp-l.antinode.info
Address: 10.0.0.9

*** alp-l.antinode.info can't find dc.fsc.com.fj: Non-existent host/domain

alp $ nslookup -type=mx FSC.COM.FJ
Server: alp-l.antinode.info
Address: 10.0.0.9

Non-authoritative answer:
fsc.com.fj preference = 0, mail exchanger = 202.62.125.193
fsc.com.fj preference = 10, mail exchanger = vmx1.connect.com.fj

Authoritative answers can be found from:
fsc.com.fj nameserver = ns43.domaincontrol.com
fsc.com.fj nameserver = ns44.domaincontrol.com
vmx1.connect.com.fj internet address = 202.62.120.18
ns43.domaincontrol.com internet address = 216.69.185.22
ns44.domaincontrol.com internet address = 208.109.255.22
alp $

Perhaps you should be using the name servers
which exist (and work), instead of
DC.FSC.COM.FJ.