This have to be defined in your DNS server. ASL is just a DNS Proxy. ASL is not a DNS server. So it is not possible to add selfdefined entries to the Proxy. You have to add the www.a.com to the DNS server to which ASL forwards (DNS Forwarder) to.
This have to be defined in your DNS server. ASL is just a DNS Proxy. ASL is not a DNS server. So it is not possible to add selfdefined entries to the Proxy. You have to add the www.a.com to the DNS server to which ASL forwards (DNS Forwarder) to.
[ QUOTE ] This have to be defined in your DNS server. ASL is just a DNS Proxy. ASL is not a DNS server. So it is not possible to add selfdefined entries to the Proxy. You have to add the www.a.com to the DNS server to which ASL forwards (DNS Forwarder) to.
[/ QUOTE ]The simplest approach, of cause, is running your own DNS server on the Internal network. Then your workstations do their DNS lookups via the local DNS server, where you can make any definitions that you want. Any DNS requests that are not satisfied by the local DNS database, will cause the DNS server to go to the outside world. This is best done by pointing it to the Astaro DNS proxy, which would then point to the ISP's DNS servers.
In short, the DNS lookups go Workstation --> Local DNS server --> Astaro DNS proxy --> ISP DNS servers --> Outside world DNS servers
I have been running this type of setup for more than 7 years now on my home network, and I have full flexibility in what DNS definitions I create. It allows me to run an unregistered "fake-net" domain on my local LAN, and to create local domain names for outside services, such as NNTP (News) that I don't proxy.
