Results 1 to 6 of 6

Thread: Different configuring policy of dns client

  1. #1
    Join Date
    Nov 2009
    Posts
    52

    Different configuring policy of dns client

    How to configure the policy of a dns client. I have a dns setup which I am trying to configure. The connection getting disappeared in between. This problem lies with the local server. May be there might be some problem with the policy settings. What should I need to do here. Also I need some information on the advance settings.

  2. #2
    Join Date
    Apr 2008
    Posts
    3,424

    Re: Different configuring policy of dns client

    To facilitate the DNS client to situate the DNSSEC OK bit in questions, you must arrange the NRPT with the appropriate or correct polices. Do not arrange any settings on the DirectAccess tab except this inaccessible right of entry technology is organized in your environment. If DirectAccess is organized in your environment, for this you have to be in touch with the DirectAccess administrator to be sure that any DNSSEC policies you genetare do not dispute with DirectAccess policies.

  3. #3
    Join Date
    May 2008
    Posts
    3,516

    Re: Different configuring policy of dns client

    When an submission uses the GetAddrInfo API or other name declaration APIs to determine a name, DNS is predictably the first protocol that is used to attempt to determine the name. If DNS fails to effectively determine the name, and if the question is a flat name, protocols such as Link-Local Multicast Name Resolution Protocol (LLMNR) and NetBIOS are tried.

  4. #4
    Join Date
    Apr 2008
    Posts
    3,339

    Re: Different configuring policy of dns client

    If DNSSEC is facilitated on a client, by evasion, failover to LLMNR/NetBIOS will happen only if the DNS client will take delivery of an authenticated denial of survival reaction. For any other failure answer, the DNS client will not fail over. Even though this performance can be customized so that the client fails over for other failure answers, DNSSEC does not present sanctuary for name resolution presented by other name service providers.

  5. #5
    Join Date
    Jan 2006
    Posts
    4,221

    Re: Different configuring policy of dns client

    Be sure to be familiar with the sanctuary risks connected with modifying this setting. It should be modified only when link-local flat name declaration is an resolved necessity. Policy disparity is relating server and client. Make sure there is no disparity between the policy arranged on a client and the trust anchors in the server to which the client concern questions.

  6. #6
    Join Date
    Jan 2006
    Posts
    3,792

    Re: Different configuring policy of dns client

    An submission can fail to determine a name if the DNS client policy on that computer necessitates DNSSEC for a name, but the DNS server to which questions are issued does not acquire the trust anchor for that zone. In this situation, either the suitable trust anchor must be added to the DNS server or the policy requiring DNSSEC on the client must be removed.

Similar Threads

  1. Replies: 3
    Last Post: 14-02-2012, 06:21 PM
  2. Windows Cannot Connect to Group Policy Client Service...
    By Jenhnrdp in forum Windows Vista Network
    Replies: 1
    Last Post: 18-05-2011, 04:45 AM
  3. Group Policy Drive Mapping Win2k DC, XP SP3 Client - Not working
    By NGV BalaKrishna in forum Active Directory
    Replies: 1
    Last Post: 11-03-2009, 03:12 AM
  4. Configuring PIX 515E, VPN Client 4.6, Windows 2003 CA
    By Oswald in forum Networking & Security
    Replies: 0
    Last Post: 04-11-2008, 04:01 PM
  5. Replies: 1
    Last Post: 13-07-2008, 12:43 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,714,007,500.35607 seconds with 16 queries