4 ms·
This is called zone transfer and is generally not enabled for obvious reasons. The protocol to look for is IXFR and I’m pretty sure dig does it.
by toxik 5y ago
This is called zone transfer and is generally not enabled for obvious reasons.
The protocol to look for is IXFR and I’m pretty sure dig does it.
- jodrellblank 5y agoApparently not obvious, or they wouldn't be asking. DNS is public data, what harm can come from asking for all of it? It doesn't leak any secrets, it doesn't take a lot of bandwidth or server load, it doesn't give you any power to imitate the domain, and it's nothing you couldn't find by brute-force eventually. It might speed up some recon "what does this company have?" but DNS caches the world over will know what the company has as soon as users reference it. For all anyone knows they could be malicious DNS caches selling the information behind the scenes. Don't put secrets in public DNS records.
- bityard 5y agoGood security practices dictate that you don't reveal any information that you don't have to.
- charcircuit 5y agoGood security practices dictate that you shouldn't rely on security by obscurity.
- ate53 5y agoDynamic responses make transfers difficult to implement in some server architectures. Which is not to take away from your point - trying to hide things in the DNS is a fairly pointless exercise.
- ate53 5y agoIXFR is for incremental transfers in which the client asks for a series of diffs between a particular serial and the current one. AXFR requests a transfer of the full zone. dig supports supports both.