AD intergrated dns, fail after primary down and client cannot use alternate dns

currently, have 2 servers 2k12 running ad integrated dns. they're both replicating each other. of clients use a static ip address.

- primary server: primary.contoso.net 192.168.100.1

- secondary server: secondary.contoso.net 192.168.100.2

- client: 192.168.100.33, preferred dns192.168.100.1/ alternate dns 192.168.100.2

after primary down, my client cannot nslookup till my client move alternate dns(192.168.100.2) preferred dns.

any solution on how automatic to let clients know secondary dns server when primary down?

any advise,

thanks regards,

sunsami mao

hi sunsami.mao,

>after primary down, my client cannot nslookup till my client move alternate dns(192.168.100.2) preferred dns.

as far know, nslookup query 1 server , has manually switched 1 server another, while "ping" command reply upon  dnsapi to name. dnsapi cycle through configured servers looking response. so, don't worry nslookup command, use ping test, if preferred dns server download, can still access related records. tested in lab, it is successful:

(preferred dns 12.12.12.12 invalid ip address can't accessed; dns 192.168.2.55 dc)

 

the result of ping , nslookup:

best regards,

anne

---

please remember mark replies answers if , unmark them if provide no help.
if have feedback technet subscriber support, contact tnmff@microsoft.com.

Windows Server  >  Directory Services