Re: Second dig lookup not the same as the first

2010-09-16 Thread Kalman Feher
For the TCP issues check your network. I'm not familiar with DLZ, but it may be worth understanding how it is effected by the addition-from-[auth|cache] options. Since you get the full response once, I presume you do not have minimal responses enabled. My ignorance of DLZ is showing, but consider

Re: Second dig lookup not the same as the first

2010-09-15 Thread Scott Haneda
Hi, No, I am not running any firewall on the client side at all. I can perform lookups elsewhere that behave as I would expect. I also performed these tests on another machine that has a more current and non Apple dig as well. The server is RHEL, not Mac OS X. I have deployed many named serv

Re: Second dig lookup not the same as the first

2010-09-15 Thread wllarso
From the output of your dig command you show that you are running a MacOSX system. Are you running the firewall on this system also? That may be dropping the TCP communication. Be aware that Apple's DNS server configrration throws every bell and whistle into the config. If you really are seriou

Second dig lookup not the same as the first

2010-09-15 Thread Scott Haneda
Hello, I have set up a new BIND/named server, being backed by DLZ in this case, though I don't think that will have any bearing on my question. This NS is not publicly known or listed as an NS anywhere as of yet, so it is only my own testing that has hit the machine. If I perform a dig request,