Hi

[EMAIL PROTECTED] wrote the following at 05:03 
07.06.2002:
>To recap:  The plan is to force internal network to resolve
>MULLAN.DNS2GO.COM to 192.168.1.128.  External requests of course will
>already find their way to 192.168.1.128 via the INTERN_SERVERS in
>network.conf

You are trying to masq a HOST in a zone you don't own. This is critical to 
your internal network because you will miss out all lot of unknown hosts in 
the zone (unless you copy them all the time.)

As I pointed out in an earlier message you have to  (somehow) _own_ the zone.

For example if you _own_ the subdomain mullan.dns2go.com then you can place 
any host you like into that subdomain, e.g. myhost.mullan.dns2go.com. This 
way you are responsible for the entire mullan.dns2go.com namespace. But 
imagine what happens if you put a _host_ mullan.dns2go.com at dns2go.com 
DNS server and then override the dns2go.com zone in your own DNS server by 
claiming authority (even just for internal use). How is your internal 
client supposed to know that the host foodle.dns2go.com needs to be looked 
up at dns2go.com whereas mullan.dns2go.com should be looked up on your 
internal DNS server.

I don't know if you can get an entire subdomain at dns2go or any other 
dynamic dns provider. But you can always get your own domain which you can 
park on one of the many dynamic DNS services which allow any doman name.

This is not really the direct answer to your question but watch out for 
such a set up.

Erich

THINK
Püntenstrasse 39
8143 Stallikon
mailto:[EMAIL PROTECTED]
PGP Fingerprint: BC9A 25BC 3954 3BC8 C024  8D8A B7D4 FF9D 05B8 0A16


_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - 
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html

Reply via email to