July 23, 201510 yr DNS logs: ==> named: info client x.x.x.x#24468: query: yah.com IN A + (y.y.y.y) DNS Query log indicating an A record query for 'yah.com' from client with IP x.x.x.x. y.y.y.y indicates the Interface IP Address of the DNS Server that received the query. This message will be logged only if 'Query Logging' is enabled on the DNS Server. ==> named: info lame server resolving 'name.xyz.com' (in 'xyz.com'?): x.x.x.x#53 This happens mostly in Internet facing DNS servers. This message indicates that a nameserver that is supposed to be authoritative for a done is actually not authoritative. ==> named: info error (unexpected RCODE REFUSED) resolving 'name.xyz.com/AAAA/IN': x.x.x.x#53 DNS server got a REFUSED response from x.x.x.x while trying to the resolve the AAAA record for 'name.xyz.com' DNS Zone Transfer Messages: ==> named: info client y.y.y.y#55618: received notify for zone 'xyz.com' DNS Server logs indicating that a NOTIFY message was received for the zone xyz.com from its Master y.y.y.y. ==> named: info zone x.x.x./IN: Transfer started. DNS Server logs indicating Zone Transfer started for the domain x.x.x.x ==> named: info zone x.x.x.x/IN: transferred serial 3658999 DNS Server logs indiating that the zone serial number of the zone x.x.x.x transferred is 3658999 ==> named: info transfer of 'x.x.x.x/IN' from y.y.y.y#53: Transfer completed: 1 messages, 6 records DNS Server logs indicating the transfer of 6 records of domain x.x.x.x is complete from the Master y.y.y.y. ==> named: err transfer of 'xyz.com/IN' from x.x.x.x#53: failed to connect: timed out Transfer failed because the server was unable to connect with the Master server x.x.x.x ==> named: err transfer of 'xyz.com/IN' from x.x.x.x#53: failed while receiving responses: REFUSED Zone transfer of domain XYZ.com was refused by the DNS Server x.x.x.x. This could be caused if the DNS server x.x.x.x is not allowing zone transfers for this domain to the DNS server that tried the transfer. Server Logs: ==> (1129 /infoblox/rc) : Appliance REBOOT Indicating server is being rebooted ==> (1633 /infoblox/one/bin/clusterd) main.c:250 cd_init(): Infoblox Startup: 5.1r3-3-111667 Indicates Server started. Log also indicates the current NIOS version Infoblox Upgrade logs: ==> (2060 /usr/bin/httpd) upgrade_administration.c:955 get_uploaded_filename(): upload Hotfix/Release file name = nios-4.3r5-1-68755-2009-07-29-21-10-16.bin Indicates the NIOS version that was uploaded ==> (9185 /infoblox/one/bin/verify_upgrade_file) : UPGRADE_GRID_STATE: Checking upgrade path... ==> (9185 /infoblox/one/bin/verify_upgrade_file) : Checking upgrade path... Server checking if there is an Upgrade path from current to the New version ==> (2020 ./upgrade.sh) : NON-LITE UPGRADE Indicating that this is a Non-Lite Upgrade ==> (927 /etc/rc.d/rc.runonce) : Upgrading NIOS, please wait... Indicating Upgrade started ==> (927 /etc/rc.d/rc.runonce) : UPGRADE_STATE: upgrade_complete ==> (927 /etc/rc.d/rc.runonce) : Upgrade complete Indicating Upgrade complete
Create an account or sign in to comment