No MX records anywhere? (BIND/FreeBSD)

>dig @localhost mx

returns no mx records, while

>dig mx

returns mx records. Something is wrong with named or my configuration, anyone know what the problem might be?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

The zone is just f***ed up.

See also my thread in http:Q_20771721.html
oskiiAuthor Commented:
The problem is that i can use my DNS to resolve other adresses, however i can not get any MX records for any domain name at all.
oskiiAuthor Commented:
The problem is not limited only to mx records as i first posted, dig will only return query and authority sections for all querys ive tried so far when using @localhost as DNS server.
Amazon Web Services

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.

Could it be your firewall, try running dmesg to see if you are blocking port 53 either tcp or udp as
in some cases dns uses tcp as well as udp.
Or more likely you are missing the file for the root of the dns system

do a dig with no parameters to get the root fileservers.

Then you also have to config it in your configuration.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
oskiiAuthor Commented:
There is no firewall present, and dig without parameters returns rootserevers, however it is not quering localhost, it asks the network dns server. dig @localhost returns no answer section, however they are all listed under the authority section. Missing the root of the dns system seems to be the most probable error, but i dont se whats wrong.
Karl Heinz KremerCommented:

No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:
Answered by HalldorG
Please leave any comments here within the next seven days.


EE Cleanup Volunteer
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.