Re: Strange DNS
- From: "Per W." <fungererikke@xxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 6 Oct 2005 09:27:00 +0200
"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx> skrev i melding
news:%23PTmNrhyFHA.2516@xxxxxxxxxxxxxxxxxxxxxxx
> In news:di1ht5$kdc$1@xxxxxxxxxxxxxxxxxx,
> Per W. <fungererikke@xxxxxxxxxxxxxxxxxxxxx> made this post, which I then
> commented about below:
>> "Deji Akomolafe" <noemail@xxxxxxxxxxxxxxxx> skrev i melding
>> news:ee7ARUeyFHA.2812@xxxxxxxxxxxxxxxxxxxxxxx
>>> Let's see....
>>>
>>> No-VPN scenario:
>>> You are trying to lookup a resource located in your office. That
>>> resource is
>>> NOT public. So, the ISP DNS server is not able to locate the record.
>>>
>>> With-VPN scenario:
>>> Now you are connected to your office. Your requests for resources
>>> inside your office are now tunnelled through the VPN connection.
>>> This way, the requests get to your office because it doesn't go
>>> through the public internet. The resource is located and the record
>>> is returned to you via the
>>> tunnel.
>>>
>>> Makes sense, or did I misunderstand you?
>>
>> Okey, let me try to explain it a litle more, when using NSLOOKUP
>> int-www.ext-office.org with or without VPN the result is NOTHING.
>
>> BUT, when using NSLOOKUP int-www.ext-office.org 194.19.1.52, thats
>> using nslookup to a external dns server, in this case a dns server
>> with a different ISP in norway, this is a dns server that everyone
>> can reach, with or without VPN, even you can use that dns server,
>
>> if
>> i do NSLOOKUP int-www.ext-office.org 194.19.1.52 without VPN then the
>> result is nothing,
>
>> BUT, when i connect to the VPN and use the same
>> lookup to the same external dns that has nothing to do with the VPN
>> connection i get the correct answer, and i get the correct answer
>> with any dns in the hole world when connected to the VPN,
>
>> but as soon
>> as i disconnect from the VPN i cant get any dns to answer,
>
>> and i cant
>> in any case with or without VPN make the internal dns-server answer,
>> even if the internal dns server has a forwarder to a dns that gives
>> an answer when connected with VPN.
>> /Per W.
>
> I can't get that either. Look:
>
> C:\>NSLOOKUP int-www.ext-office.org 194.19.1.52
> Server: dns202.telia.com
> Address: 194.19.1.52
>
> *** dns202.telia.com can't find int-www.ext-office.org: Non-existent
> domain
>
Yes thats rigth, you get the same strange error that i get, BUT as soon as i
connect to the head office with VPN the dns202.telia.com find the correct IP
for that adress, and the dns202.telia.com has NOTHING to do with the company
i connect to with VPN, all dns-servers around the world will answer correct
as soon as i am connected with VPN, i cant see why its should bee like this,
and why couldnt the internal DNS server solve this adress when conencted
with the VPN as all other dns servers can.
/Per W.
.
- Follow-Ups:
- Re: Strange DNS
- From: Ace Fekay [MVP]
- Re: Strange DNS
- References:
- Strange DNS
- From: Per W.
- Re: Strange DNS
- From: Deji Akomolafe
- Re: Strange DNS
- From: Per W.
- Re: Strange DNS
- From: Ace Fekay [MVP]
- Strange DNS
- Prev by Date: Re: DNS Update Failed
- Next by Date: Re: DNS not updating
- Previous by thread: Re: Strange DNS
- Next by thread: Re: Strange DNS
- Index(es):
Relevant Pages
|