Coincidenatlly, I had just setup NDNS manually (yet again) (with flush DNS) before reading your post.
re > Are you using the NortonDNS client, or did you change your settings manually?
Settings manually - not using NDNS client. Was unsure how reliable reversal with NDNS client.
re > Are you able to ping both of the DNS server addresses: 184.108.40.206 and 220.127.116.11?
C:\Windows\system32>ping 18.104.22.168 Pinging 22.214.171.124 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 126.96.36.199: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Windows\system32>ping 188.8.131.52 Pinging 184.108.40.206 with 32 bytes of data: Reply from 220.127.116.11: bytes=32 time=19ms TTL=56 Reply from 18.104.22.168: bytes=32 time=20ms TTL=56 Reply from 22.214.171.124: bytes=32 time=21ms TTL=56 Reply from 126.96.36.199: bytes=32 time=20ms TTL=56
Ping statistics for 188.8.131.52: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 21ms, Average = 20ms
Is my NIS11 SafeWeb component compatible with NDNS SafeWeb component. Two SafeWeb components called to act on url resolution ?
Tried Ping several times with same results.
Firefox can't find the server at mail.yahoo.com on first try. Second try slow. Third try is faster.
Firefox can't find the server at hotmail.com on first try. Second try slow. Third try is faster.
Seems like I'm training NDNS.
Maybe I should try 194.1 as Preferred and 192.1 as Alternate ?
I've been running tests on 184.108.40.206 from around the world and we haven't seen any errors. I even went back to that week and we had 100% availability from all 15 sites globally.
Unfortunately, while switching the order might help, the reality is that both IPs are used if they exist. I think that the only way to test this is to use ONLY the 194.1 address to see if you still see these errors.