The offices are connected via VPN using Cisco ASA 5505 (VPNclient config rather than Site to Site) connecting back to an ASA 5510 at head office.Other offices connected in the same way work when another doesnt.The primary DNS is our one in the 172.16.0.012 space, the secondary is 8.8.8.8 to allow access to the internet in case the VPN tunnel drops for any reason.
I think this could be caused by the DNS cache being flushed as part of this - the Windows DNS cache makes the intermittent problem look less so because it caches failed lookups as well as successful ones. However, it is possible some other aspect of Windows is involved. You could also capture on the dns server, say with network monitor, to see if the requests are getting there. Also I would make sure that they dont have a statically assigned IP and DNS server. I would also look into a pc at that location acting as a DNS MITM. Its a fairly basic and well-known issue, but one to check nonetheless. Tunnel two or more networks together that are using the same non-public IP address ranges, and one has to deal with address and routing conflicts. Provide details and share your research But avoid Asking for help, clarification, or responding to other answers. ![]() Not the answer youre looking for Browse other questions tagged windows domain-name-system or ask your own question.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |