Find the answer to your Linux question:
Results 1 to 2 of 2
We currently have a large IP pool derived from multiple datacenters and upstream providers. At the present moment, when we want to change the rDNS settings of a particular IP, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Nov 2009
    Posts
    1

    Public DNS Server Questions


    We currently have a large IP pool derived from multiple datacenters and upstream providers. At the present moment, when we want to change the rDNS settings of a particular IP, we are at the mercy of the IP provider's time table. This time table is too slow for our needs as the staff at the providers are simply too slow to respond. To remedy the problem, we want to establish our own DNS infrastructure so we can be in charge of changing the rDNS records and no longer be dependent on the IP providers resources.

    This need for rDNS setting control is a top priority project, but we do not have experience setting up and/or maintaining such systems. We are looking for some help to start developing this system. Many questions exists for which we do not have the answers for such as:

    1) What problems will face (if any) trying to set up a centralized DNS / rDNS system for IPs with exist on multiple networks from multiple ASN from multiple datacenters?
    2) How do we handle propagating to the rest of the DNS severs out there?
    3) How much infrastructure is really needed to maintain these DNS records?

  2. #2
    Linux Guru Lazydog's Avatar
    Join Date
    Jun 2004
    Location
    The Keystone State
    Posts
    2,677
    Quote Originally Posted by ZenNetworks View Post
    1) What problems will face (if any) trying to set up a centralized DNS / rDNS system for IPs with exist on multiple networks from multiple ASN from multiple datacenters?
    Reverse DNS is always an issue when the IP Address owner doesn't delegate the range to your DNS Server to resolve.

    2) How do we handle propagating to the rest of the DNS severs out there?
    The only propagating you do is to your own DNS servers. What you need to do is have each domain setup to use your DNS servers as its DNS resolver.

    3) How much infrastructure is really needed to maintain these DNS records?
    DNS is not that heavy depending on the amount of queries you receive.

    The questions are as follows:


    1. How many zones/domains will be hosted?
    2. How many queries against each zone/domain?
    3. How many DNS server will you need (minimum of 2)?
    4. What type of hosting ae you going to be providing?

    You are going to need at least 2 DNS server. Most Domain providers require 2 server minimum before they will delegate the zone lookup. Your biggest questions are going to be #1 & 2. They will pretty much dictate what type of machines you will require.

    Regards
    Robert

    Linux
    The adventure of a life time.

    Linux User #296285
    Get Counted

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •