MX record is returned when doing a nslookup, however, I've already deleted this MX record

I'm having DNS issues.  I deleted a MX record on my Win 2003 DNS server, however, when doing a nslookup set type=mx command on the mail domain it still returns.  I've deleted this record, how is it still being returned?
gopher_49Asked:
Who is Participating?
 
Giuseppe "Pino" De FrancescoSenior Solution ArchitectCommented:
From the DNS server where you have the secondary zone, right click on the zone and choose "Reload From Master"

Cheers
Pino
0
 
gopher_49Author Commented:
below are the results of the nslookup.......  This record doesn't exist.

C:\WINDOWS\system32>nslookup
Default Server:  drexel_1.drexel.com
Address:  192.168.1.250

> set type=mx
> drexchem.com
Server:  drexel_1.drexel.com
Address:  192.168.1.250

Non-authoritative answer:
drexchem.com    MX preference = 10, mail exchanger = mail.drexchem.com

mail.drexchem.com       internet address = 192.168.1.2
>
0
 
Giuseppe "Pino" De FrancescoSenior Solution ArchitectCommented:
Hiya,
Non-authoritative answer means that is not an info stored in the SOA DNS, so... I think that you have more than one DNS server,so just force the replica.

Cheers
Pino
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
bwalker1Commented:
First, clear the cache from DNS management on your server, and also run ipconfig /flushdns on your client.
0
 
NJComputerNetworksCommented:
below are the results of the nslookup.......  This record doesn't exist.

C:\WINDOWS\system32>nslookup
Default Server:  drexel_1.drexel.com
Address:  192.168.1.250

> set type=mx
> drexchem.com
Server:  drexel_1.drexel.com
Address:  192.168.1.250

Non-authoritative answer:   <---- THIS RECORD WAS NOT FOUND ON YOUR LOCAL WINDOWS 2003 DNS SERVER.
drexchem.com    MX preference = 10, mail exchanger = mail.drexchem.com

mail.drexchem.com       internet address = 192.168.1.2
0
 
NJComputerNetworksCommented:
if it was, it would have said AUTHORITATIVE Answer...
0
 
gopher_49Author Commented:
Pino,

How do I force a replica to each DNS server?
0
 
NJComputerNetworksCommented:
from my location, i get this:

drexchem.com    nameserver = ns02.worldspice.net
drexchem.com    nameserver = ns01.worldspice.net
mail.drexchem.com       internet address = 216.37.73.243
0
 
gopher_49Author Commented:
I've cleared the cache, I also took away the external DNS server from it's DNS server settings on it's control panel.  Whether I have a MX record in my DNS database, or, if one is not there, I get the same results as listed above.
0
 
NJComputerNetworksCommented:
You get this too?

drexchem.com    nameserver = ns02.worldspice.net
drexchem.com    nameserver = ns01.worldspice.net
mail.drexchem.com       internet address = 216.37.73.243

...and you want to change this IP address? if so, you need to make the change on the Internet...not on your local internal DNS servers...

Goto worldspice.net and change your MX record.
0
 
Giuseppe "Pino" De FrancescoSenior Solution ArchitectCommented:
Er... Assuming that your SOA is on your servers...
0
 
NJComputerNetworksCommented:
Looks like you need to go to http://www.dotster.com/ to change this DNS record...
0
 
gopher_49Author Commented:
Pino,

I have two DNS servers.  Both replicate via Active Directory.  The primary DNS server is called drexel_3, and secondary is called drexel_1.  Both of these DNS servers are providing DNS for the domain drexel.com (My local domain), however, I'm created a local MX record for my mail domain, which is called drexchem.com.  This record is only accessed from the computer in my local network.  Now, I right click on my secondary server's (drexel_1) drexel.com zone and left click on 'reload'.   It let me do this once, however, it later said 'Failed to reload zone.  The zone is locked for zone transfer or update.'   Both zones within each server seem to have the same records.  I only have one MX record and they both have the same one.
0
 
gopher_49Author Commented:
NJComputerNetworks,

I'm referring to the MX record on my local network.  I only want to change how the computer inside my perimiter network resolve the MX record.  The external DNS resolution (for internet queries) is fine...  
0
 
gopher_49Author Commented:
Pino,

I only have a zone for drexel.com.  Should I create a zone for drexchem.com also?
0
 
NJComputerNetworksCommented:
Yes, you would need to create a zone for drexchem.com if you want to control records in the drexchem.com namespace locally (internally).

Once you do this, you will have to create an MX record in this new zone.

Also, you should add a new DNS Suffix for all of you clients...  drexchem.com.  You can do this in TCP/IP properties of any machine.  Click the DNs tab.

A DNS suffix will automatically append the FQDN name to each lookup...

for example,

if you have DREXCHEM.com and Drexel.com listed as DNS suffixes on each clients...this behavior will occur...

When the client searches for server1...both drexel.com and drexchem.com will be appended automatically in the search.  So, server1.drexel.com and server1.drexchem.com will be searched for...  
0
 
gopher_49Author Commented:
I created a zone called 'drexchem.com'.  I also created a A record and a MX record.  When I do a nslookup type for a MX record for the domain drexchem.com the server IP address is returned.  I thought this would fix a problem I'm having sending emails out through my front end server, however it did not, regardless, I have the MX record created so that's one less thing to worry about.  I posted my original problem in the Exchange section, hopefully it will be resolved there.  For now, creating the drexchem.com zone allowed me to properly resolve the MX and A record.

thanks
0
 
Giuseppe "Pino" De FrancescoSenior Solution ArchitectCommented:
Yep, you have to create the zone in your DNS servers as Primary Standard Zone (in one of them) and as Secondary Standard Zone (pointing to the primary as Master) in your secondary DNS server. CAREFUL to add the domain also in the "DNS Domain" of the Forwarders tab of the Properties page of your servers, and for this  UNcheck the setting "Do not use recursion for this domain" and add as forwarders your external DNS servers.

Cheers
Pino
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.