shadow_man
Executive Member
Hi,
I'm in a mixed environment.
Linux, OSX and Windows.
I use AD for DNS. I'm having a weird issue at the moment. All of the hosts are using the same DNS servers (AD)
Windows host:
ping hostname.example = INSTANT resolution and ping reply.
Linux host:
ping hostname.example = IP resolves instantly, but delay of about 30 sec per packet, but response times on packets themselves are normal.
---
I've used NSLOOKUP to confirm that DNS resolution is working correctly, which it is and DNS resolution is instant, but pings are not.
I've changed the Linux boxes to use Google's DNS and as such resolution is instant and pings are instant.
It's clearly an issue with my DNS server (AD) and its clearly reverse DNS related as if I add a PTR for the troublesome host, then resolution / ping becomes instant on the Linux hosts.
Any advice? I'm a bit lost as to why this used to work 100% , but since Friday its been giving issues and wants me to add custom PTR records to have prompt resolution / ping replies.
EDIT: Tested the Mac's and they don't suffer this issue - possibly they don't look for a PTR and reverse DNS every packet like Linux does?
Any ideas?
Thanks,
I'm in a mixed environment.
Linux, OSX and Windows.
I use AD for DNS. I'm having a weird issue at the moment. All of the hosts are using the same DNS servers (AD)
Windows host:
ping hostname.example = INSTANT resolution and ping reply.
Linux host:
ping hostname.example = IP resolves instantly, but delay of about 30 sec per packet, but response times on packets themselves are normal.
---
I've used NSLOOKUP to confirm that DNS resolution is working correctly, which it is and DNS resolution is instant, but pings are not.
I've changed the Linux boxes to use Google's DNS and as such resolution is instant and pings are instant.
It's clearly an issue with my DNS server (AD) and its clearly reverse DNS related as if I add a PTR for the troublesome host, then resolution / ping becomes instant on the Linux hosts.
Any advice? I'm a bit lost as to why this used to work 100% , but since Friday its been giving issues and wants me to add custom PTR records to have prompt resolution / ping replies.
EDIT: Tested the Mac's and they don't suffer this issue - possibly they don't look for a PTR and reverse DNS every packet like Linux does?
Any ideas?
Thanks,
Last edited: