I have resolved this by moving DNS management of hosted domain to another server (Using Bind DNS).

Keep in mind that such things are called "DNS Rebinding" attacks. Many DNS servers filter this by default and you might run into issues if you for example use a laptop that needs to

If you're connecting from browser attack, presumably browser would have access to the private DNS infrastructure (otherwise it could be firewalled from whatever sensitive services are running).

(Quote)

With the way DNS works, no external client can just "list" all the records you have and get your "map", unless AXFR is allowed (which is disabled by default in name

As somebody who has multiple subnets at home I wouldn't want a map of them anywhere public so I keep my DNS internal. (Image)

I use VPN and don't have a problem using host file for local lookup. In Tomato just tick "Intercept DNS port (UDP 53)". I use three letter names for all the computers here and also v

The advantage of using a public DNS server instead of .local domains is that it also works e.g. through a VPN. You can just connect to your network from anywhere in the world, push the routes for the

I run one used just by my local recursor (not public-facing), so that my own domain keeps resolving at home in case [both] Internet links go down. And yes I do use public DNS for RFC1918 and IPv6 ULA

They do resolve, so a need for an internal or external DNS server in some special cases doesn't have to exist.

(Quote)

Does anybody run their own DNS servers at home anymore?

Do you mean having your Internet router serve these DNS entries?

It doesn't hurt. It only affects those who use your DNS server.

Not quite. Most home routers are running a DNS proxy and return 192.168.0.1 or whatever themselves.

RFC1918 IP's in public DNS servers is somewhat frowned upon and some providers of caching/forwarding nameservers will block them from appearing (I think openDNS offers such an option).

Well home dns on your own lan could be nice: you set up a simple resolver and you add your own custom domains (pdnsd could do that easily). Once cached locally everything will be faster and more secur

I do this! No issues so far, with cloudflare for DNS.

hosts file. Works even if I use like 3 different DNS server per protocol (3 for IPv4 and 3 for IPv6). Make it globaly work? I replace the hosts file of the gateway.

http://serverfault.com/questions/4458/private-ip-address-in-public-dns