Re: set up a LAN DNS so that it doesn't conflict with external DNSes
Quoting Jerome Lacoste (Frisurf) <lacostej@frisurf.no>:
> Hei,
>
> My current setup it, seen from the outside
> - www.mydomain.com points to a server located at our ISP
> - xxx.mydomain.com points to our LAN thanks to a redirection using DDNS.
> - our router redirects requests incoming from the outside to one
> internal server (let's say 192.168.1.2)
>
> >From the inside, www.mydomain.com still resolves to the web site located
> at our ISP, but xxx.mydomain.com resolves to our LAN External IP and is
> blocked by our router. To overcome this difficulty I decided to install
> a local DNS server (also advised by some people on this list)
>
> My needs are the following:
> - from my LAN I want that the address xxx.mydomain.com resolves directly
> to our server (192.168.1.2).
> - I want all my former settings to work. I.e. www.mydomain.com resolves
> to the ISP located site.
>
> I managed to do the first step. Unfortunately, my bind configuration
> made is so that I couldn't resolve www.mydomain.com anymore. Everything
> else (google, slashdot) resolves correctly.
>
> I tried to play with BIND's configuration through webmin, but I didn't
> make it work as expected. Worse I broke my first working step.
>
> Any idea on how to set this up?
>
Several alternatives:
1) Fix your router.
2) Create a zone file for xxx.mydomain.com, not mydomain.com. Note:
you must duplicate all services present at the external IP on the
internal server for this to work properly. This may be difficult.
3) Use an internal address instead, e.g. server.internal.lan. You
will need to run an internal DNS server also for this to work.
I have used 1) and 3) successfully. I do not have any easy way to try
out 2), so implementer beware.
HTH,
Jeffrey
Reply to: