MariaJoseK asked:
I have two servers running CentOS release 6.5 (Final).
In one of them is installed FreeIPA:
Name: freeipa.fi.example.com
IP: 192.168.99.50
And the other Zimbra as mail server:
Name: freeipa.fi.example.com
IP: 192.168.99.2
In FreeIPA I created a mx record and then update changes.
The dns works well for both servers not so with mx registry:
nslookup freeipa.fi.example.com
Server: 192.168.99.50
Address: 192.168.99.50#53
Name: freeipa.fi.example.com
Address: 192.168.99.50
nslookup zimbra2014.fi.example.com
Server: 192.168.99.50
Address: 192.168.99.50#53
Name: zimbra2014.fi.example.com
Address: 192.168.99.2
nslookup
> set q=mx
> fi.example.com
Server: 192.168.99.50
Address: 192.168.99.50#53
*** Can't find fi.example.com: No answer
In fact, the query doesn’t work for the zone:
nslookup fi.example.com
Server: 192.168.99.50
Address: 192.168.99.50#53
*** Can't find fi.example.com: No answer
Add information from my records:
@
NS
freeipa.fi.example.com.
MX
MX
1 zimbra2014
_kerberos
TXT
FI.EXAMPLE.COM
_kerberos-master._tcp
SRV
0 100 88 freeipa
_kerberos-master._udp
SRV
0 100 88 freeipa
_kerberos._tcp
SRV
0 100 88 freeipa
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs
SRV
0 100 88 freeipa
_kerberos._tcp.dc._msdcs
SRV
0 100 88 freeipa
_kerberos._udp
SRV
0 100 88 freeipa
_kerberos._udp.Default-First-Site-Name._sites.dc._msdcs
SRV
0 100 88 freeipa
_kerberos._udp.dc._msdcs
SRV
0 100 88 freeipa
_kpasswd._tcp
SRV
0 100 464 freeipa
_kpasswd._udp
SRV
0 100 464 freeipa
_ldap._tcp
SRV
0 100 389 freeipa
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs
SRV
0 100 389 freeipa
_ldap._tcp.dc._msdcs
SRV
0 100 389 freeipa
cliubuntu
A
192.168.99.100
SSHFP
1 1 910E5A8D2BFDC24FCBEA45B226C4207FE81C86FD
SSHFP
1 2 618A4FBDB24C7901419994277CA661D7D16428D6A5F411D64EB4F487 07144CFC
SSHFP
3 1 CEEDC3C8A58D7DE59C8F60FCBDF13CCBF19F35D4
SSHFP
3 2 C1AA6110C2E488728D38B655ADC8D9700B6A409998FC7740A58BC0D8 EAC8F430
SSHFP
2 1 E2D3038DEA31D5083E1778204BD9F1EF9A6FE732
SSHFP
2 2 3F10D2F1ABFBDB8FB3460010D18B8ABD9E370CD2324362A7C31579C5 0E9BF8C0
freeipa
A
192.168.99.50
SSHFP
1 1 462CCB5D17640703E0731BCF4A1454862967EEA3
SSHFP
2 1 65517CB8AB7ABAC3A27E9F4700071AFC09D165EF
zimbra2014
A
192.168.99.2
MX
1 zimbra2014
SSHFP
1 1 04DA2757EC4999C2609D1706F622EF18F4A86654
SSHFP
2 1 E671A5DD87C98EFCBC966899454FAAA620720F51
SSHFP
1 1 15D9E62B7D6169544C6F28BC385E2F482C6E92E4
SSHFP
2 1 6881D66C21E879DA5A0C6B1732A2EB02BC347CAC
I’ve been looking for a long time and I still can’t fix it.
Do you suspect that is missing in this configuration?.
I appreciate so much your help :).
Greetings!.
My answer:
Aha, I see the problem now. You have given the hostname MX an MX record.
The MX record should be attached to the domain, and not have an individual hostname (unless you are trying to divert mail for a subdomain, which is rare).
To resolve the problem, delete the invalid record and add the MX record to the @ name.
View the full question and any other answers on Server Fault.
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
The post has no MX record appeared first on Ringing Liberty.