<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffcc" text="#000000">
My method for solving this problem is to have a local DNS with two
views:<br>
- internal view (recursing), responding to internal clients with
local addresses<br>
- external view (not recursing), that is used as a hidden master for
my DNS-provider<br>
<br>
No forwarding, the local server does all its own resolving, the
hidden master controls all the outside servers.<br>
<br>
The downside is that you must maintain both views, typically with
different data, unless you only have public addresses. Some
management tool might be a good solution for this.<br>
<br>
The good side is that your laptop users will not have to know
whether they are inside or outside your network - e.g. your
mailserver is mail.domain.com in all cases, inside it has a
192.168.x.x address and outside it has a.b.c.d so mail programs
never see any difference.<br>
<br>
On 05/01/11 9:17, Fidel Viegas wrote:
<blockquote cite="mid:4D2428FC.4070008@kazomosolutions.biz"
type="cite">Hi everyone!
<br>
<br>
First and foremost, Happy New Year!
<br>
<br>
Secondly, this is my first post in this list and my first
<br>
question is part technical, part administrative. Basically,
<br>
I have hosted a webserver with a hosting company,
<br>
who also manages my domain. Now, I have decided to
<br>
setup a local mail server that is going to be part of the
<br>
domain managed by the hosting company (e.g. mail.domain.com).
<br>
That has been set ok, and it is all working. However,
<br>
I have also configured a local DNS to resolve our
<br>
internal names. The internal nameserver is setup as
<br>
a caching nameserver that forwards to the
<br>
hosting company's nameserver, and is also setup as
<br>
a primary nameserver that manages the zone for the
<br>
local domain (domain.local). That is all ok as well.
<br>
The problem comes when the managers decided that
<br>
they want the local domain the same as the
<br>
global domain (e.g. domain.com). We can't really setup the
<br>
global nameserver on our facilities because we experience quite a
<br>
lot of power outage and also have Internet connectivity
<br>
problems from time to time.
<br>
<br>
Can someone suggest me an approach to resolve this issue without
<br>
getting conflicts between the local nameserver
<br>
and the hosting company's nameserver?
<br>
<br>
Thanks in advance!
<br>
<br>
Best Regards,
<br>
<br>
Fidel.
<br>
_______________________________________________
<br>
bind-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>