• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 895
  • Last Modified:

DNS and Bind and MX record different from DNSSTUFF


I have an issue were when i run a dig or a host command on my network using my DNS machines.  I get differnent information then what DNSSTUFF.com reports.

when i run the following command
host -t -mx alliance-mktg.com
My DNS reports alliance-mktg.com is an alias for resalehost.networksolutions.com
if i run this command dig alliance-mktg.com
I get the following ip address  
However when i use DNSSTUFF they report totally different informations
All this is causing my mailserver to not be able to send email to this domain.  
Can someone tell me why MY DNS is reporting different information then that which DNSSTUFF is reporting?  And what my best course of action is to remedy.

  • 2
  • 2
1 Solution
I'm getting the same results as dnsstuff.com shows me...

the two mx records for alliance-mktg.com are:
 mx01-dom.earthlink.net and

the report on dnsstuff.com indicates that it queried one of the root servers, and that's how my DNS is configured as well (no forwarders)

for starters, I think that you need to flush the cache on your DNS server and see if that helps
shrek2Author Commented:
I did flush it before you posted this.  And that did update my records. I did a Dig and it shows what DNSSTUFF shows.  However i am still not able to get an e-mail through.  
I think this issue is resolved. But since i have you here do you know why i would get this message when running rndc flush

no key definition for name key

This is the first i've noticed this.  Bind still works but rndc doen't seem to function all rndc commands give this error. ?


I don't use rndc myself, but I know that it requires keys to interact with named...rndc.conf and named.conf have to have matching keys...

Here's a couple of links to check out:


shrek2Author Commented:
I have an include statement in my named.conf to look at my rndc.key and the key matches that which is in rndc.conf.  I will check your links if i find what i need i will credit you.

cat /etc/resolv.conf

You're pointing to your local DNS server.  Your local DNS server has either cached outdated info, or is providing outdated info in a zone file.  Check if dig or nslookup reports that your local nameserver is offering the outdated info as a "non-authoritative answer" or not; if it is, then it's cached data, if it's not (is authoritative), then it's from a local zone file.
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.

Join & Write a Comment

Featured Post

Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now