Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm having problems setting up my DNS and would like to send a screenshot of my DNS settings to a support desk. Now I wonder how sensitive this DNS data is. Are all records public? Or should I be careful who I hand this information to?

share|improve this question

All records are public if you make them public - is the server they're on publicly accessible? If you query the records from your home computer, can you get a response for the domain's records?

The other aspect to this is that enumeration of the records isn't generally possible for the public - so, even if someone knows you have, doesn't mean they know about the name, or which IP address it points to. An AXFR zone transfer is the type of DNS request that would provide a full list of everything in the zone, and public DNS servers typically prevent these queries from being answered.

A full list of the zone may potentially provide interesting information to an attacker - but if it's a public zone with no entries that are 'hidden', then you're not exposing anything that someone can't get at with an internet connection and DNS client.

share|improve this answer
The IP addresses and domain names of internal servers will definitely be of interest to an attacker. If they can leverage a poorly configured proxy server or a vulnerable internet-facing system on the network, they can use the information they gained to scan internal systems for services and potential vulnerabilities. – Polynomial Jan 25 '12 at 9:14
On the flipside, a support desk for a hosting company is likely to be a safe group to reveal server configuration information to. They're the ones who you pay for the service, so hacking you wouldn't make any sense. Of course, you should still never reveal any passwords. – Polynomial Jan 25 '12 at 9:19

Generally speaking, it's reasonably easy to figure out what a site's IP range is, and then reverse to what amounts to a full zone dump. So if this is externally available zone data, it's likely not a huge issue. Internal stuff is perhaps more sensitive.

But really, they'll just need to know the general format, I would expect, so if you're concerned, redact the actual names to something you feel comfortable with:

IN MX 10

might become

IN MX 10

or similar.

Also, unless the issues revolve around particular records, you could probably truncate your zone files considerably, so long as they have all the relevant record types, SOA, values, etc.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.