I have an active directory domain HEALTHEXAMPLE (no .local).
There are 2 x DCs. DC01.HEALTHEXAMPLE and DC02.HEALTHTEXAMPLE. Both of the DCs is my DNS Servers too.
I discovered (through struggling to apply group policies) that "nslookup healthexample" does not work. I can also not access \healthtech\sysvol (because of this I assume).
C:\Users\Administrator>nslookup healthexample
Server: DC01.healthexample
Address: 10.10.10.1
*** DC01.healthtech can't find healthexample: Non-existent domain
C:\Users\Administrator>nslookup healthexample dc02.healthtech
Server: DC02.healthexample
Address: 10.10.10.2
*** DC02.healthtech can't find healthexample: Non-existent domain
However, when I query this from a linux machine using bind-tools' "dig" command, I do get a result:
rtyr@server ~ $ dig @10.10.10.1 healthtexample
; <<>> DiG 9.16.15 <<>> @10.10.10.1 healthtexample
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57706
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;healthtexample. IN A
;; ANSWER SECTION:
healthtexample. 600 IN A 10.10.10.2
healthtexample. 600 IN A 10.10.10.1
;; Query time: 6 msec
;; SERVER: 10.10.10.1#53(10.10.10.1)
;; WHEN: Wed Sep 29 20:07:16 SAST 2021
;; MSG SIZE rcvd: 71
What could the reason for this be? I checked my DNS servers and healthtexample has 2 x A records pointing to 10.10.10.1 and 10.10.10.2 respectively.
Both machines are running Windows Server 2019 Standard