Unable to understand why a different A record response being sent by bind

2016-06-20 Thread Harshith Mulky
I am Running bind (bind-9.9.5P1-2.2.2.x86_64) on Open Suse 13.2 I have the following Records in my Zone file $ORIGIN test1.com. $TTL 600 @ IN SOA atlanta.test1.com. admin.test1.com. ( 2003022720 ; Serial 5680

Re: Unable to understand why a different A record response being sent by bind

2016-06-20 Thread Nico CARTRON
Hi Harshith, On 20 June 2016 at 15:05:58, Harshith Mulky (harshith.mu...@outlook.com) wrote: I am Running bind (bind-9.9.5P1-2.2.2.x86_64) on Open Suse 13.2 I have the following Records in my Zone file $ORIGIN test1.com. $TTL 600 @  IN  SOA atlanta.test1.com. admin.test1.com.  (

Re: Unable to understand why a different A record response being sent by bind

2016-06-20 Thread Matus UHLAR - fantomas
On 20.06.16 13:05, Harshith Mulky wrote: I have the following Records in my Zone file denver1.test10.com. IN A10.54.80.17 test10.com clearly does not belong here... denver2.test1.com. IN A10.54.80.150 IN A10.54.80.35 When I am doing a dig for the record denver2.test1.com

Query "resolver" and "lwresd" via "dig"

2016-06-20 Thread Jun Xiang X Tee
Dear all, I wish to know efficient ways to query "resolver" and "lwresd". To my understanding, "resolver" is the iterative full DNS resolver, and "lwresd" is the lightweight resolver daemon. I plan to use "dig" to query both of them. I am not able to find a way to query "resolver" using "d