1) source does DNS lookup for the FQDN "dest.example.com".
2) source's DNS server is co-resident on the ingress tunnel router
and performs a lookup in the global DNS for a well-known prefix
appended to the FQDN suffix, e.g.: "egress.example.com".
3) source's DNS server gets back locators for the egress tunnel
router from the global DNS, then sends an IP-in-IP encapsulated
RFC4620 Node Information Query asking the egress tunnel router
to resolve the FQDN "dest.example.com".
4) egress tunnel router returns identifers associated with
"dest.example.com"; ingress tunnel router caches the resolution
and returns the resolution to the source as response to the
"real" DNS query.
What happens when I type "ping <global-address>" on the source? What if DNS is down, do I lose global connectivity? What if one of the two domain names don't exist in DNS? What if network administrators are totally against making routers DNS servers? What if your ITR is a low- end router where it can store both the DNS cache and mapping database?
What I am trying to say is, some things need to go into the network and some things should just stay out of the network.
Dino -- to unsubscribe send a message to rrg-request@psg.com with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg