[THIN] Re: Netscaler DNS question
- From: Pat Coughlin <strangedog@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Wed, 27 Mar 2013 20:47:44 -0400
Just create A records for your XenApp Servers directly on the netscaler?
On Wed, Mar 27, 2013 at 3:28 PM, Tim Anderson <timothylanderson@xxxxxxxxx>wrote:
> Thanks for the reply Pat.
>
> I know how to enable XML DNS resoltuion, what has me stumped is how do I
> keep my non direct access clients happy when I enable XML DNS resolution.
> My netscaler only looks to my external BIND server for DNS resolution and
> it knows nothing of my internal DNS structure. I trying to figure out how
> to be able to delegate my internal DNS zone (e.g.
> internal.myorganization.com) to be resolved by my netscaler on the
> internal DNS servers. Unfortunately I cannot just add the internal DNS
> servers to the mix because we maintain an internal version of our external
> top level domain.
>
>
> On Wed, Mar 27, 2013 at 1:08 PM, Pat Coughlin <strangedog@xxxxxxxxx>wrote:
>
>> I think this is what you are looking for. Direct Access customers are
>> likely not coming through your netscaler anyway (as once they are on the
>> VPN, they are internal users). You need to ensure your netscaler can
>> resolve the FQDNs or your external customers are screwed, however,,,
>>
>> Pat Coughlin
>> CCIA and all around Citrix Goon
>>
>> http://support.citrix.com/article/CTX128436
>>
>> *Summary*
>>
>> This article describes how to enable XML *DNS Address Resolution* in
>> XenApp 6.
>>
>> *Requirements*
>>
>> XenApp 6
>>
>> *Background*
>>
>> Enabling *DNS Address Resolution* is allows the XenApp 6 server to
>> return the Fully Qualified Domain Name (FQDN) of the XenApp server to the
>> ICA client using the XML Service. This also means that workstations must be
>> able to resolve the FQDN of the XenApp 6 servers with this policy enabled.
>>
>>
>> On Wed, Mar 27, 2013 at 1:58 PM, Tim Anderson <timothylanderson@xxxxxxxxx
>> > wrote:
>>
>>> I did see that technote, in that instance the netscaler is authoritative
>>> for a domain. My netscalers are not authoritative for any domains, I put
>>> an NS record in BIND for the particular records that my handles.
>>>
>>>
>>> On Wed, Mar 27, 2013 at 11:28 AM, Aljets, Paul
>>> <PAljets@xxxxxxxxxxxxxxx>wrote:
>>>
>>>> I’m not sure if this is what you’re looking to do, but a cursory
>>>> search on google returned this for you.****
>>>>
>>>> ** **
>>>>
>>>> http://support.citrix.com/article/CTX110488****
>>>>
>>>> ** **
>>>>
>>>> ** **
>>>>
>>>> --paul****
>>>>
>>>> ** **
>>>>
>>>> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
>>>> Behalf Of *Tim Anderson
>>>> *Sent:* Wednesday, March 27, 2013 9:23 AM
>>>> *To:* thin@xxxxxxxxxxxxx
>>>> *Subject:* [THIN] Netscaler DNS question****
>>>>
>>>> ** **
>>>>
>>>>
>>>> I'm hoping someone on the list has encountered this previously and can
>>>> give me some guidance. We maintain different DNS authority servers for our
>>>> external DNS domain (e.g. myorganization.com) on our internal and
>>>> external networks and for this reason I have never had my netscalers
>>>> looking to my internal DNS servers to resolve any queries. My netscalers
>>>> are cruising along just fine using the external DNS servers.
>>>>
>>>> The team implementing Microsoft Direct Access has informed me that they
>>>> need me to change the behavior of the XML service to respond with the DNS
>>>> name rather than the IP of a XenApp server.
>>>>
>>>> To do this I would need to have the netscalers look to the internal DNS
>>>> servers to resolve queries for the XenApp servers (e.g.
>>>> internal.myorganization.com)
>>>>
>>>> I don't know how to delegate this DNS zone to the internal DNS servers
>>>> in netscaler. Any advice or suggestions would be greatly appreciated.
>>>>
>>>> TIA****
>>>>
>>>
>>>
>>
>
Other related posts:
