Skip to main content

Slave/Secondary DNS Server (Read Only DNS Server) How AXFR & IXFR Works in DNS for Zone Transfer ?



Slave/Secondary  DNS Server (Read Only DNS Server)

How AXFR & IXFR Works in DNS for Zone Transfer  ?

The term slave simply indicates that a name server will obtain the zone records using zone transfer operations but will answer authoritatively for the zone for as long as it has valid zone data (defined by the expiry field of the zone’s SOA RR). The term slave in no sense implies priority of access. As previously described, slave servers will be accessed, in general, just as frequently as any master name server. Slave servers may also transfer their zone files to other slave servers.

 


The Zone Transfer between Master Server and Secondary Server
What is AXFR ?

AXFR Transfer: The DNS polling process is accomplished by the slave name server sending a query to the zone master requesting the SOA RR. If the SOA RR’s serial number is greater than the current one maintained by the slave name server, a full zone transfer (AXFR) is requested by the slave DNS. This is the reason it is vital to be disciplined about updating the SOA serial number every time anything changes in any of the zone records


The Serial number format may be used as follows ;

YYYYMMDDSS:
For e.g 2014010800 -- > Serial number of a  zone training.com
           
If there is any change of Record for e.g Change of A Record or update of Record of the zone training.com
The new Serial number will be -à  2014011000
Next Serial number will be -à 2014011001(the Last 2 Digit will increase by 1 number if there are multiple change of record for the same zone file in one day)


What is  IXFR Transfer(Incremental Zone Transfer):

IXFR Transfer(Incremental Zone Transfer): Transferring very large zone files can take a long time and waste bandwidth and other resources. It is especially wasteful if only a single record has been changed! RFC 1995 introduced the incremental zonetransfer (IXFR), which (as the name suggests) allows the slave name server and master name server to transfer only those records that have changed.The process works as for AXFR. The slave name server sends a query for the domain’s SOA RR to the zone master every refresh interval. If the serial number of the SOA RR is greater than the one currently stored by the slave, the name server requests a zone transfer and indicates whether or not it is capable of accepting an IXFR. If both master and slave name servers support the feature, an IXFR takes place; otherwise, an AXFR takes place. IXFRs use TCP on port 53


Comments

Popular posts from this blog

Password Expiry notification for the users in zimbra 8.x within 7 Days for the email users

This Script will run as cron tab daily basis and it will alert the users for whom password is going to expire within 7 days. It will also alert admin for the users for whom password expired. Kindly replace the domain.com with your own domain name and the  /opt/zimbra/postfix-2.10.3.2z/sbin/sendmail  path to the actual path of postfix #!/bin/bash #Script for zimbra password expiry email notification. # Meant to be performed as daily cronjob run as zimbra user.  # redirect output to a file to get a 'log file' of sorts. # Time taken of script; echo "$SECONDS Started on: $(date)" # Set variables: # First notification in days, then last warning: FIRST="7" LAST="3" # pass expiry in days, we are assuming passwd exiry is 150 Days POLICY="150" # Sent from: FROM="admin@domain.com" # Get all users - it should run once only. USERS=$(ionice -c3 /opt/zimbra/bin/zmprov -l gaa domain.com) #Todays date, in seconds: DATE

How to Create a Delegated Admin Account in Zimbra 8.x

How to Create a Delegated Admin Account in Zimbra 8.x. Create a File as shown below with the contents .  Replace the domain.com and helpdesk Email id with your domain and helpdesk (Delegated Admin ) Name. #vi admindelegate #!/bin/bash # $1 domain.com # $2 helpdesk zmprov ma $2 zimbraIsDelegatedAdminAccount TRUE zmprov ma $2 zimbraAdminConsoleUIComponents cartBlancheUI zimbraAdminConsoleUIComponents domainListView zimbraAdminConsoleUIComponents accountListView zimbraAdminConsoleUIComponents DLListView zmprov ma $2 zimbraDomainAdminMaxMailQuota 0 zmprov grantRight domain $1 usr $2 +createAccount zmprov grantRight domain $1 usr $2 +createAlias zmprov grantRight domain $1 usr $2 +createCalendarResource zmprov grantRight domain $1 usr $2 +createDistributionList zmprov grantRight domain $1 usr $2 +deleteAlias zmprov grantRight domain $1 usr $2 +listDomain zmprov grantRight domain $1 usr $2 +domainAdminRights zmprov grantRight domain $1 usr $2 +configureQuota zmprov g

sendmail complete cofiguration with pop3 and squirrelmail

Sendmail Introduction Sendmail implements a general purpose internetwork mail routing facility. This document explain how to install sendmail and run an email server which will send and receive mail using the SMTP protocol. An IMAP or POP3 server is required to retrieve mail using Eudora or MS Outlook. Sendmail does not offer POP3 or IMAP services. Installation Prerequisites You should have a basic knowledge of UNIX and DNS. The server should allow incoming connections to the SMTP service which will be listening on TCP port 25. The server should have a fully qualified hostname (FQDN) such as mail.example.net. The hostname should resolve to an A record. It should not be a CNAME. The MX record for the domain for which you wish to receive mail should point to the hostname of your server. There should a PTR record for the IP address of your server. Mail from your server may be rejected if there is no reverse DNS. Installing sendmail Download the sendmail