Hi, I find lots of information on isatap and translation between ipv4 and ipv6, tunneling etc. I come to grasp how clients can talk to each other over an IPv6 tunnel in the different use cases. But I do find little information about how DNS comes into the picture and which updates a client should do. We see here that a client on the local network deletes A and AAAA record and then only adds the AAAA record from the isatap interface. When we do an ipconfig/registerdns , then it deletes A and AAAA record and adds both A and AAAA again. putting this in a logon script could solve our issue. But what when the isatap interface reinitiates for some reason? bye bye A record? What I am wondering about is if this is the default behavior of an internal client. And if there are any changes we can make to change the behavior so that both A and AAAA record get registered on boot. The A record is needed so that non IPv6 clients can find it via dns. Client is Windows 7

Hi, Can you advise me What kind of DNS server you are currently using? You may kindly check whether you let your client register its address in DNS. Please refer to the following steps to check accordingly: 1. Open your Network Connections 2. Right –click your Network adapter Which you are currently using. 3. Then hit Properties, click TCP/IP ipv4. 4. Click Advanced, hit DNS tab. Then check whether you select the check box before Register this connection’s addresses in DNS. I suspect your issue is caused by the DNS server’s dynamic update. So you need to check your DNS server. If your issue still persists, please post your thread at Windows Server Forums.