>> 1) A good server software must be flexible to allow build different
solutions.
>Granted, but between boundaries.
>> 2) To use different services on one interface we use ports, but not
virtual interfaces.
>As Samba is trying to emulate a Microsoft Active Directory domain, we
>are limited by the ports that Microsoft uses.
>> 3) When we use services we (in almost all configurations I saw) provide
host:port.
>Agreed, but, again we are limited by what Microsoft uses.
>> So, it is absolutely normally to make DNS forwarding not to IP, but to
IP:port.
>Not in AD and I cannot really remember seeing anything to do with AD
>that suggested using other than the ports Microsoft uses.
>> 4) If we follow your logic that users can create un-tested and
unworkable installations
>> we need to forbid system administrators to edit configuration files.
>You can create untested installations, that is how you find they may be
>unworkable, it is just that I have seen most of the unworkable
>installations.
?
I don?t see any problems with the ports that Microsoft uses if I add to samba
configuration
"dns forwarder = x.x.x.x:non_53_port"? instead of "dns forwarder
= x.x.x.x", do you?
?
--
Best regards, Alex Orlov