kshounish5.bigleap.com IN A 126.96.36.199
kshounish5.bigleap.com IN A 188.8.131.52
kshounish7.bigleap.com IN A 184.108.40.206
kshounish8.bigleap.com IN A 220.127.116.11
kshounish9.bigleap.com IN A 18.104.22.168
kshounish10.bigleap.com IN A 22.214.171.124
DNS Database records
The database records used in zone file are called as standard resource records or sometimes, just “RRs”. All records have the same basic format:
Syntax Name In type data
In previous example
@ IN SOA kshounish2.love.com. email@example.com. (
2000011301 ; serial
3600 ; refresh
900 ; retry
1209600 ; expire
43200 ; default_ttl
can be described as follows
@: It means from the origin to the lastname object that is bigleap.com.
In: This stands for Internet servers
SOA: This stands for `Start Of Authority’. It marks the beginning of a zone’s data and defines the parameter that affects the entire zone. Followed by the current machine name where the DNS server is maintained. And, the administrator login, which can be used while DNS is not working.
20000011301;serial: This is the serial number--a numeric value that tells or notifies the slave server, that the database has been updated. So slave server should also update it.
3600;refresh: This is the refresh cycle in seconds. In every refresh cycle the slave server comes to master server and checks for the updated database.
1800;retry: This particular line refers to the retry cycle which in turn means that the slave server should wait before asking the master server again in case master server doesn’t respond.
1209600;expire: This is the time for slave server to respond to queries of client for the expiration time if master server fails and has to be up and not getting up. After this period slave server also fails to solve the queries of clients and sits idle.
432100;default_ttl: This refers to the default time to leave, for this domain to work for, when named is once started. Remember the user doesn’t have to play with this unless he wants that the query time from the slave server should be somewhat less or more. In case we want to change, we should change only the refresh time in both master and slave. The best way is to make it 2, which means after each 2 seconds slave server will query to master server.