03-20-2019 09:17 AM
i recently shifted my zone from MS server to infoblox there is some observation that whenever i do nslookup it gives me 2 X time out for every query and than resolve also for the query for which my server is authoratitive.
when i switch back to MS or on my bind it is OK.
I understnad that some time nslookup is not recomended but if this happen on Infoblox it must happen on other platform.
right now i cannot install dig utility to test .
Any body have clue is there anything i am missing.
03-20-2019 01:40 PM
Let me start with a couple of simple questions.
1. Do you have both v4 and v6 enabled on this Windows client? You can confirm this by navigating to ncpa.cpl-->Ethernet Properties
2. This could be because of DNS suffixes. You can confirm this by navigating to ncpa.cpl-->Ethernet Properties-->Ipv4 Properties-->Advanced-->DNS-->Append these DNS suffixes.
To workaround suffixes in nslookup you can perform the query with a period in the end. (www.example.com. instead of www.example.com)
3. If you run 'nslookup' in the following fashion, do you experience the same problem?
server 10.X.X.X // Specify your authoritative IB DNS server
set q=a // This specifies that you are querying for an 'A' record
www.example.com // Your DNS A record query FQDN
01-05-2021 08:53 PM
Can this thread be re-opened/looked at?
I'm having a similar issue whilst we are on VPN using Cisco AnyConnect, but we are mainly using Infoblox as our DNS. nslookup using another Infoblox appliance still shows DNS request time outs. Often times it would resolve after two tries, but some other DNS names in our environment never return with a response (but internally it resovles fine)