I can't get my NAP Clients to search for a _HRA._TCP DNS Record in the Domain. It's just looking for a record in the site and nowhere else.
If I create a SRV Record like _hra._tcp.<sitename>._sites.<domainname> it does work. So the Discovery is enabled and working. All fine.
But if I delete that record and instead create one in _hra._tcp.<domainname> the client never tries to resolve that name.
I've used Network Monitor and can see that the domain joined client (Windows 7) does not even try to do a DNS Lookup for that SRV Record which is odd.
A manual NSLOOKUP for _hra._tcp works and gives the right info, but as mentioned above, the client is not even trying to find that address.
C:\Users\administrator>nslookup Default Server: UnKnown Address: 192.168.0.10> set type=srv> _hra._tcp Server: UnKnown Address: 192.168.0.10 _hra._tcp.domain.local SRV service location: priority = 10 weight = 10 port = 443 svr hostname = lfnap02.domain.local _hra._tcp.domain.local SRV service location: priority = 10 weight = 10 port = 443 svr hostname = lfnap01.domain.local lfnap02.domain.local internet address = 192.168.0.14 lfnap01.domain.local internet address = 192.168.0.13 > quit
From my point of view, the Discovery is setup correctly because it can find and resolve the Site SRV Record if it exists.
The clients are using DHCP and have the Primary DNS Suffix set.
C:\Users\administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : LFCLI01 Primary Dns Suffix . . . . . . . : domain.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : domain.local System Quarantine State . . . . . : Not Restricted Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : domain.local Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter Physical Address. . . . . . . . . : 00-15-5D6F-1F-20 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::b55d:95d2:c634:711a%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.104(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : den 18 mars 2013 13:45:44 Lease Expires . . . . . . . . . . : den 4 april 2013 10:41:37 Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.10 DHCPv6 IAID . . . . . . . . . . . : 234886493 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-CF-44-0F-00-15-5D-6F-1F-20 DNS Servers . . . . . . . . . . . : 192.168.0.10 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.domain.local: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : domain.local Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes
Anyone who's run into something similar, or have any advice for a solution?
Thanks all,
Markus Lassfolk