DNS and Bind and MX record different from DNSSTUFF

Posted on 2005-04-13
Last Modified: 2012-06-21

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 reports.

when i run the following command
host -t -mx
My DNS reports is an alias for
if i run this command dig
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.

Question by:shrek2
    LVL 16

    Expert Comment

    I'm getting the same results as shows me...

    the two mx records for are: and

    the report on 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

    Author Comment

    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. ?


    LVL 16

    Accepted Solution

    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:


    Author Comment

    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.

    LVL 7

    Expert Comment

    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.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Better Security Awareness With Threat Intelligence

    See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

    Network Interface Card (NIC) bonding, also known as link aggregation, NIC teaming and trunking, is an important concept to understand and implement in any environment where high availability is of concern. Using this feature, a server administrator …
    SSH (Secure Shell) - Tips and Tricks As you all know SSH(Secure Shell) is a network protocol, which we use to access/transfer files securely between two networked devices. SSH was actually designed as a replacement for insecure protocols that sen…
    Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…
    Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

    760 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    13 Experts available now in Live!

    Get 1:1 Help Now