Question

Many nameservers use a file backend configuration whereas some use a database backend allowing for instant DNS updates. What are the PROS and CONS

Answer 1

Answer:

Pros:
1. Proprietary and open source firewall and interruption uncovering services
2. Remote transfer black-holing and bandwidth capacity agreement with Tier 1 upstream provider
3. Proprietary and open source DDoS mitigation devices
4. Distributed communications monitoring that utilize internal and third party monitor services
5. Heavily enforced employee access control and in order disclosure policies
6. Automated zone judgment on all DNS Servers

Cons:
1. Your TTL (Time to Live) settings —

•     You can set the TTL for each DNS documentation in your field name's zone file. TTL is the moment in time period for which servers hoard the in sequence for your DNS records.
• For example, if you set the TTL for an exacting record to one hour, servers store the in sequence for that record locally for an hour before retrieve updated in sequence from your trustworthy name           

Head waiter.

•   Shorter TTL settings make can increase transmission speed. However, shorter settings also boost the amount of queries to your convincing name server, and that greater than before load slow your server's    meting out time.

2. Your ISP (Internet Service Provider) —

• Your ISP caches DNS proceedings (stores the data locally rather than retrieve fresh data from your DNS server) to momentum up Web browsing and reduce
• Transfer, which slows your broadcast time. Some ISPs pay no attention to TTL settings and only update their cached records every two to three days.

3. Your domain name's registry —

• If you change your area name's name servers, we communicate your change request to the registry surrounded by minutes, and they publish your trustworthy NS (name server) records to their root zone.
• Most registries update their zones promptly. For example, VeriSign refresh zones for .com domain names each three minutes. However, not all registries make update that quickly. Registries often protect their root name servers from overuse by setting a high TTL of up to 48 hours or more for those NS records.
• In addition, even though recursive name servers should not cache the root NS records, some ISPs cache the in sequence anyway, which can result in a longer Christian name server broadcast time.