I have a problem resolving mx record for madronafoods.com on my dc.
nslookup return
Name: madronafoods.com
Address: 62.0.58.94
while when try mx record
set type=mx
DNS request timed out. for madronafoods.com
timeout was 2 seconds.
I can't change my primary DNS as it has to be my DC
when I try nslookup on another ISP I am getting correct mx record
Non-authoritative answer:
madronafoods.com mail exchanger = 0 madronafoods-com.mail.protection.outlook.com.
this problem Is only with a single domain. and my email server can't send and email without resolving mx.
what can case such problem what is the simple way to resolve it without changing hosts file manually and changing primary DNS server (has to be my DC)
ExchangeDNS
Last Comment
Jan Bacher
8/22/2022 - Mon
Dr. Klahn
Create an MX record in your DC's DNS database.
Jan Bacher
The real question is: why can't your DNS server find an MX record?
Are you going any forwarding with your DNS to another server?
leop1212
ASKER
yes.
it am forwarding to my ISP DNS ns1.hvdata.net which is my ISP dns and I also tried first forward it to 4.2.2.2 still same results.
when I use 4.2.22.2 on my ws as primary dns it resolves mx for madronafoods. fine but not on my local DC or local net which points to my local DC dns.
Jan Bacher
Have you restarted DNS on your dc to flush the cache?
Because, unless you have the domain name configured internally, it should look up the correct information.
; <<>> DiG 9.10.4-P2 <<>> madronafoods.com mx @192.168.2.61 +trace
;; global options: +cmd
. 3600 IN NS e.root-servers.net.
. 3600 IN NS i.root-servers.net.
. 3600 IN NS m.root-servers.net.
. 3600 IN NS l.root-servers.net.
. 3600 IN NS k.root-servers.net.
. 3600 IN NS j.root-servers.net.
. 3600 IN NS b.root-servers.net.
. 3600 IN NS f.root-servers.net.
. 3600 IN NS g.root-servers.net.
. 3600 IN NS c.root-servers.net.
. 3600 IN NS h.root-servers.net.
. 3600 IN NS a.root-servers.net.
. 3600 IN NS d.root-servers.net.
;; Received 460 bytes from 192.168.2.61#53(192.168.2.61) in 0 ms
Pinging outlook.com [132.245.81.130] with 32 bytes of data:
Reply from 132.245.81.130: bytes=32 time=73ms TTL=235
Reply from 132.245.81.130: bytes=32 time=72ms TTL=235
Reply from 132.245.81.130: bytes=32 time=73ms TTL=235
Reply from 132.245.81.130: bytes=32 time=73ms TTL=235
Ping statistics for 132.245.81.130:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 73ms, Average = 72ms