M
manoa
Guest
I have two w2k3 enterprise domain controller in a single forest-domain setup.
Everything has been fine and working for 2 years now. We to shut all our
systems down this past weekend due to electrical maintenance of the building.
When we power all the servers backup, we did not have any problem except for
one. We discovered that our local DNS MX record is not correct when we use
nslookup to query the record. When I run the set query=mx command, we are
getting the lowest priority MX record. I have 3 MX record that has an A
record with the associated IP as well as PTR. When I ping each mail server
IP, I get the correct netbios name but for some reason the MX query only come
back with one MX record and its the last preference. The higher priority MX
(MX record with the lower preference) does not even display when the query is
run. I checked the dns record of the ISP and it display correct. All the MX
record display in its correct IP and preferences. The two servers hosting
our local DNS points to itself and the other as the preferred and alternate
DNS. I looked at both servers DNS manager and everything is correct. This
issue is entering it second day. Although we continue to receive email, our
spam appliance is not working properly because of this DNS issue.
Everything has been fine and working for 2 years now. We to shut all our
systems down this past weekend due to electrical maintenance of the building.
When we power all the servers backup, we did not have any problem except for
one. We discovered that our local DNS MX record is not correct when we use
nslookup to query the record. When I run the set query=mx command, we are
getting the lowest priority MX record. I have 3 MX record that has an A
record with the associated IP as well as PTR. When I ping each mail server
IP, I get the correct netbios name but for some reason the MX query only come
back with one MX record and its the last preference. The higher priority MX
(MX record with the lower preference) does not even display when the query is
run. I checked the dns record of the ISP and it display correct. All the MX
record display in its correct IP and preferences. The two servers hosting
our local DNS points to itself and the other as the preferred and alternate
DNS. I looked at both servers DNS manager and everything is correct. This
issue is entering it second day. Although we continue to receive email, our
spam appliance is not working properly because of this DNS issue.