What type of MPLS VPN is being used? What was the reason for migrating to MPLS? Have you considered deploying a WINS server for single named resolution? if integrity and encryption are required)

Also check any relevant filter actions through right-clicking on the IP Security Policies node -> Manage IP filter lists and filter actions (i.e.

See if any of the policies listed over the right-hand side dictate that IPSec is required for DNS (might be implicit rather than explicit, so check all the rules).

Local computer or Another computer -> name of domain controller.

IP Security Policy Management -> Add button.From an administrative command prompt, launch mmc.exe.The easiest way to check this out is to load up the IPSec Policies MMC either on your computer whilst running as a domain admin, or while locally logged on to the domain controller: This would at least explain why L2TP/IPSec connections would be registering while MPLS wouldn't. This may or may not be scoped to just the VPN range. It sounds like you may have an IPSec policy defined requiring IPSec enforcement for DNS. They simply do not seem to be able to register their DNS with the DC's. Clients resolve DNS, affected by ADUC changes, Group Policy, etc. (sometimes they keep their subnet, sometimes they get a new one)Īll other domain controller functions work perfectly. Migration to MPLS occurs and registration ceases. screaming profanities -> makes me feel better (good)Īll clients on an IPSEC network register without issue.

TCP/IP -> DNS -> 'Register this connection's addresses in DNS (good).ipconfig /registerdns (returns errors above).telnet connection over port 53 to primary DNS server (good).ping host name or ip of primary DNS server (good).I am having issues with some of my remote sites that have been migrated from IPSEC VPN to MPLS.Įvent ID: 1014 | Name resolution for the name timed out after none of the configured DNS servers responded.Įvent ID: 11164 | The system failed to register host (A) resource records (RRs) for network adapter settings: bla bla bla

Wireshark display filter reverse dns