What is the advantage, if any, of running one's own DNS server? Surely the link between domain name and IP address must already have been established?
I suppose a lot of it depends on your needs. For us, we run internal DNS servers for all the VMs we have running; mostly for software development and monitoring. It makes sense for us to do so as we have mostly Macs (and my Linux workstation) that work better using DNS. Had we been a mostly Windows shop, we'd likely use NetBIOS internally with some Dynamic DNS for win clients.
We also have external DNS servers for our cloud based servers, web servers primarily. We could have stuck with Network Solutions (our Domain Registrar) for DNS, but we have a LOT of domains across the globe and we prefer handling them ourselves. Management can be a bit of a headache at time, but it's worth it, IMHO.
On Mon, Jun 22, 2015 at 8:14 AM, Timothy Murphy gayleard@eircom.net wrote:
What is the advantage, if any, of running one's own DNS server? Surely the link between domain name and IP address must already have been established?
-- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 6/22/2015 5:27 AM, Mark Haney wrote:
I suppose a lot of it depends on your needs. For us, we run internal DNS servers for all the VMs we have running; mostly for software development and monitoring. It makes sense for us to do so as we have mostly Macs (and my Linux workstation) that work better using DNS. Had we been a mostly Windows shop, we'd likely use NetBIOS internally with some Dynamic DNS for win clients.
actually, Windows networks preferably use DNS now too... netbios is a legacy thing, been deprecated since windows 2000.
On Mon, Jun 22, 2015 at 01:14:56PM +0100, Timothy Murphy wrote:
What is the advantage, if any, of running one's own DNS server? Surely the link between domain name and IP address must already have been established?
DNS servers *are* the link between domain name and IP address. Someone has to run it, there is no other way to 'establish' it.
Like any service (such as web services, mail, cloud), the choice of whether to host it yourself or pay someone else to host it really boils down to what you use it for. If you only have a small handful of domain names that rarely update, don't bother. If you have a dynamic, complex infrastructure, it might make sense.
Am 2015-06-22 14:14, schrieb Timothy Murphy:
What is the advantage, if any, of running one's own DNS server? Surely the link between domain name and IP address must already have been established?
Hi,
about which scenario are you talking? You have an authoritative DNS server in mind, or a recursive DNS server, or a caching only nameserver? Different kind of setups for different purposes.
Alexander
On 2015-06-22, Timothy Murphy gayleard@eircom.net wrote:
What is the advantage, if any, of running one's own DNS server? Surely the link between domain name and IP address must already have been established?
As others have said, it depends on your circumstances and what you want to achieve. In my case I run dnsmasq on my home network, configured to use my ISP's DNS server as its upstream. For me the advantages are that it allows me to address connected devices by name and to see at a glance what devices are connected.
And for me the advantage is I get to have name resolution on my internal machines.
On Sunday, July 05, 2015 14:57:22 Liam O'Toole wrote:
On 2015-06-22, Timothy Murphy
gayleard@eircom.net wrote:
What is the advantage, if any, of running one's own DNS server? Surely the link between domain name and IP address must already have been established?
As others have said, it depends on your circumstances and what you want to achieve. In my case I run dnsmasq on my home network, configured to use my ISP's DNS server as its upstream. For me the advantages are that it allows me to address connected devices by name and to see at a glance what devices are connected.