Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > Cisco > DNS doctoring, alias .

Reply
Thread Tools

DNS doctoring, alias .

 
 
AM
Guest
Posts: n/a
 
      03-15-2005
Does the DNS doctoring work without specifing protocols and ports or does it with them as well?
Are internal DNSes needed for the doctoring to work properly or is it the same thing to have clients with external DNSes
specified and answers from them are anyway translated?

Alex.
 
Reply With Quote
 
 
 
 
Martin Bilgrav
Guest
Posts: n/a
 
      03-15-2005

"AM" <(E-Mail Removed)> wrote in message
news:8jxZd.14401$(E-Mail Removed)...
> Does the DNS doctoring work without specifing protocols and ports or does

it with them as well?

yes, you can use the alias command completly "stand-alone"
look at the Cisco doc for "understanding the Alias command"
There are two usage guidelines there: one is DNS doctoring, other is
destination NAT

> Are internal DNSes needed for the doctoring to work properly or is it the

same thing to have clients with external DNSes
> specified and answers from them are anyway translated?
>
> Alex.



 
Reply With Quote
 
 
 
 
AM
Guest
Posts: n/a
 
      03-15-2005
AM wrote:

> Does the DNS doctoring work without specifing protocols and ports or
> does it with them as well?
> Are internal DNSes needed for the doctoring to work properly or is it
> the same thing to have clients with external DNSes specified and answers
> from them are anyway translated?
>
> Alex.


I tried to use external DNSes and mapped a PC as web server using a static rule specifying protocols and ports.
It seems not to work.
Does it work only if the questioner is a DNS and not a client?
I flushed the DNS cache of my client.

Please, help me.

Alex.
 
Reply With Quote
 
AM
Guest
Posts: n/a
 
      03-15-2005
AM wrote:

> AM wrote:
>


Say the name foo.bergladu.edu is mapped to 1.2.3.4

I tried

static (inside,outside) 1.2.3.4 192.168.30.235 dns netmask 255.255.255.255 0 0

and resolving the name with the external DNSes where the name foo.bergladu.eduis mapped

this this the output of nslookup

C:\>nslookup foo.bergladu.edu
Server: <my primary DNS external name>
Address: <external DNS primary IP>

Nome: <real name of the the mapped IP >
Address: 192.168.31.235
Aliases: foo.bergladu.edu

If I specify

static (inside,outside) tcp 1.2.3.4 80 192.168.30.235 80 dns netmask 255.255.255.255 0 0

this is the output

C:\>nslookup foo.bergladu.edu
Server: <my primary DNS external name>
Address: <external DNS primary IP>

Nome: <real name of the the mapped IP >
Address: 1.2.3.4
Aliases: foo.bergladu.edu


Why is there this difference? Is it correct?

should be the options "dns" work in each case?

Alex.
 
Reply With Quote
 
AM
Guest
Posts: n/a
 
      03-16-2005
Martin Bilgrav wrote:
> "AM" <(E-Mail Removed)> wrote in message
> news:8jxZd.14401$(E-Mail Removed)...
>
>>Does the DNS doctoring work without specifing protocols and ports or does

>
> it with them as well?
>
> yes, you can use the alias command completly "stand-alone"
> look at the Cisco doc for "understanding the Alias command"
> There are two usage guidelines there: one is DNS doctoring, other is
> destination NAT


I read the document and you are correct but I saw a different behaviour specifying protocol and ports (it seems not to
work) and stand alone (all thing go OK).
My proposal is to use DNS doctoring but I can't.
Perhaps my previous posts were a bit confused but briefly (and willing to give access to a web server to internet users
and to PCs on internal LAN)

static (inside,outside) tcp interface www 192.168.30.21 www netmask 255.255.255.255 0 seems NOT to work to me

static (inside,outside) interface 192.168.30.21 netmask 255.255.255.255 0 works properly for me

I would the first one to work, i.e. it must resolve name with internal IP of the web server.

My PIX runs 6.3(4) OS version.

Alex.
 
Reply With Quote
 
Martin Bilgrav
Guest
Posts: n/a
 
      03-16-2005

"AM" <(E-Mail Removed)> wrote in message
news:dSXZd.15532$(E-Mail Removed)...

> static (inside,outside) tcp interface www 192.168.30.21 www netmask

255.255.255.255 0 seems NOT to work to me
>
> static (inside,outside) interface 192.168.30.21 netmask 255.255.255.255 0

works properly for me


you can specify a "DNS" command into that static - Did you try that ?


 
Reply With Quote
 
AM
Guest
Posts: n/a
 
      03-16-2005
Martin Bilgrav wrote:

> "AM" <(E-Mail Removed)> wrote in message
> news:dSXZd.15532$(E-Mail Removed)...
>
>
>>static (inside,outside) tcp interface www 192.168.30.21 www netmask

>
> 255.255.255.255 0 seems NOT to work to me
>
>>static (inside,outside) interface 192.168.30.21 netmask 255.255.255.255 0

>
> works properly for me
>
>
> you can specify a "DNS" command into that static - Did you try that ?
>
>


I'm really sorry Martin I was out of my mind when writing and I forgot "dns" in both statements.
The correct post had to be

static (inside,outside) tcp interface www 192.168.30.21 www dns netmask 255.255.255.255 0 seems NOT to work to me

static (inside,outside) interface 192.168.30.21 dns netmask 255.255.255.255 0 works properly for me

Alex.
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
reference/alias in perl vs reference/alias in C++ grocery_stocker C++ 9 05-24-2008 04:32 AM
XP X64 Pro, IE7, Delphi 2007, IntraWeb, MS Access, ODBC Alias problem: Insufficient memory for this operation. Alias: SomeDatabase. Skybuck Flying Windows 64bit 13 01-09-2008 07:34 PM
PIX 501 DNS Alias on interface for static IPs while port fowarding and DHCP? wonknose@gmail.com Cisco 3 04-29-2006 10:14 AM
PIX DNS rewrite vs Alias PES Cisco 0 07-17-2004 08:45 PM
Web Reference and DNS Alias Francois Guerin ASP .Net Web Services 0 01-28-2004 02:46 PM



Advertisments