DNS problem - nslookup appends domain name and resolves IP address to the server's public ip
Posted on 2008-10-01
Server 2003 has DNS problems and e-mails are getting stuck in the exchange queue. This is what nslookup looks like (using experts-exchange as a test):
C:\Documents and Settings\Administrator>nslookup
Default Server: ns-rec.isp.wdc.eggn.net
There are two problems that I see:
1. Company.net is the AD domain name and it is appended to the end of each answer
2. 66.7.x.x is the public IP of the company's server (the WAN IP) and is obviously incorrect
The server has 2 NICS with active directory and DNS enabled. The firewall is in bridging/invisible mode and one of the NICS on the server is WAN and the other is LAN.
And this is what an MX lookup looks like:
> set type=mx
primary name server = no-dyn-updates.san.yahoo.com
responsible mail addr = postmaster.san.yahoo.com
serial = 2008100101
refresh = 10800 (3 hours)
retry = 3600 (1 hour)
expire = 7084000 (81 days 23 hours 46 mins 40 secs)
default TTL = 28800 (8 hours)
What the heck is going on? No matter the MX record, it always ends up with a Yahoo name server.
I should also add that this a server I just took over admin duties for. The previous technician had disabled DNS on the server back in April and was just relying on the ISP's DNS servers.
I started work on the server a few days ago and turned on DNS and configured it as I usually do. That's when the problem started. And it looks like most e-mails are going out except for about a dozen domains.