Wildcards in MX Record Domain Names

Jim Reid jim at rfc1035.com
Fri Dec 17 20:25:39 UTC 1999


>>>>> "Rainer" == Rainer Ginsberg <Rainer.Ginsberg at de.bosch.com> writes:

    >> The point is that an internal root implies there is no need to
    >> resolve external names. (Save for things like firewalls and
    >> proxy servers at the perimiter net.) So if someone has decided
    >> to implement this, why should they re-introduce external names
    >> to the internal name space?

    Rainer> You do not introduce external names. Because the MX
    Rainer> records point to your own mail relays which will then use
    Rainer> Internet MX records. And those internal legs of my mail
    Rainer> relays of course have internal names.

But these MX records are for external names - *.de, *.com, *.net, etc,
etc - that by implication were not supposed to be visible in the
internal root zone. Sure, the targets of these MX records are internal
hosts, but that is not the point.

It all comes down to how much of the real root name space you're
prepared or forced to import into that internal root zone. I prefer a
clean and clear separation between the two, though other people have a
different stance. That's their choice. After all they're the ones
running their nets.


More information about the bind-users mailing list