VPN Client: Register this connections addresses in DNS The result: when a client is connected to the company vpn server I can resolve the client's host name using nslookup - in other words, the company dns server "knows" the client (but nslookup - ptr does not work - only A record can be "seen") But I do not see this host name (say Home-Laptop) in the DNS console! I even made the export of the forward zone to the txt file and was searching
Trying to Federation with company using Office 365. SRV Record issue . . . By default, NSLookup looks for A records In this case, the _sipfederationtls record is an SRV record As such NSLookup won't resolve it properly To verify the validity of your SRV record, do the following: c:\>nslookup >set type=srv >_sipinternaltls _tcp domain com
nslookup - social. technet. microsoft. com Here is one more moment nslookup is made by client (DNS client requester) requesting dns zone transfer (from dns server to dns client)
DNS not working on standalone HV server As Azarya says above, you should see the default nameserver when you type nslookup at a command prompt The default will be the DNS server that is configured on the preferred adapter
nslookups result - incorrect IP address 72. 52. 194. 126 When I run nslookup command and lookup my domain as the following Its result is strange IP address (72 52 194 126) instead of xx xx 65 30 I run the command on both DC and clients then the