On 2014-10-11 21:44, lleachii.aol.com wrote:
The issue is only on my DNS server. I have a zone transfer from 44.in-addr.arpa and ampr.org, so a copy of the zones are located on my BIND server at 44.60.44.3
On the host system you are using what does /etc/resolv.conf show (or equiv on eg Windows systems)?
What does a 'dig @44.60.44.3 44.in-addr.arpa' result in?
What is the exact configuration of the zone in BIND look like?
I've been using nslookup to look at the records from multiple machines. It only occurs on certain IPs where the fourth octet is less than 10.
nslookup is extremely bad for debugging DNS as it hides a lot of problems and status details.
Note that you might just see a delay for the queries you are making as you are triggering the AXFR (transfer) of the zone file during that time. Hence, enable debugging in BIND and watch the log file.
And/or run a wireshark on the server and see what network traffic gets generated.
I'll try dig as well.
Dig is the only way to go.
Greets, Jeroen