Answered by:
DirectAccess DNS static/cname entry problem

Question
-
I'm setting up DirectAccess server using RTM version, everything appears to be working fine. I can ping internal IPv6 hosts from both internal network and external network, file accessing is also fine. But I cannot access any DNS entry which are manually created, including both static A and CNAME record. But if I ping the the actual host name, it works fine. For example, the server is called SRV1, and it has a CNAME called INTRAWEB. I can ping SRV1 internally and externally, but I cannot access INTRAWEB host both internally and externally.Friday, August 21, 2009 7:12 PM
Answers
-
The problem is solved now, everything is tested ok so far. Now I need to convert all possible servers to IPv6 to make DA working.
- Proposed as answer by Joe DaviesMicrosoft employee Monday, August 24, 2009 7:47 PM
- Marked as answer by Miles Zhang Friday, August 28, 2009 1:34 AM
Monday, August 24, 2009 1:02 PM
All replies
-
Hi Daniel,
Try the following:
1. When the DirectAccess client is on the intranet, verify that it has successfully performed intranet detection with the netsh name show effective command. There should be no entries in your Name Resolution Policy Table (NRPT). If so, the problem is not with DirectAccess, but with the DNS client and server.
2. Check the permissions associated with the static and CNAME entries (the Security tab on the properties of the entries) to ensure that the user or computer account of the DirectAccess client can at least read these entries.
Friday, August 21, 2009 9:31 PM -
I see. When the client is in intranet, it still shows the NRPT table. Is it because my NLS server is not working? I noticed that when I run DA wizard, it keeps saying my NLS server is not reachable, but I can actually visit the https://nls.<domainname>/ in IE. Did I miss something for NLS? I thought it's very easy set up, just an empty web site with SSL certificate, isn't it?
Friday, August 21, 2009 11:35 PM -
I know the problem with my NLS server now, coz' there is nothing in the site, it returns 403. I just put a default iis page, now DA wizard says validation successful. I will test it again Monday.Friday, August 21, 2009 11:42 PM
-
The problem is solved now, everything is tested ok so far. Now I need to convert all possible servers to IPv6 to make DA working.
- Proposed as answer by Joe DaviesMicrosoft employee Monday, August 24, 2009 7:47 PM
- Marked as answer by Miles Zhang Friday, August 28, 2009 1:34 AM
Monday, August 24, 2009 1:02 PM