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.
Didn't find your answer? Ask the community — no account required.
M
Martin Bilgrav
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
same thing to have clients with external DNSes
A
AM
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.
A
AM
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
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: Address:
Nome: 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.
A
AM
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)