David,

thanks for letting me know that this is a bug. Please tell me, do you think this would actually be an extra hop that would delay the delivery of the package? We are having problems with a DNS server not resolving names fast enough and we suspect this is the cause.

 many thanks in advance,

 fdo

[EMAIL PROTECTED] wrote On 09/13/06 12:50,:

Fernando,

I have two systems named fdo5 and fdoclt4. All the NICs in both systems are connected to the same switch. fdoclt4 has 3 zones in it. When I traceroute from fdo5 to any of the zones, the route has an extra hop (always 18.1.1.142). shouldn't this example resolve to 18.1.1.145 itself? Is there any way to correct problem?


I believe you're seeing a side effect of the following bug

     6426172 ICMP Destination unreachable from global zone instead
         non-global

This issue is being resolved and there should be a fix in an upcoming
Nevada build.

dsc


--
<http://www.sun.com>      * Fernando Castano *
Staff engineer, MDE

*Sun Microsystems, Inc.*
260 Constitution Drive
Menlo Park, CA 94025 US
Phone x88904/+1 650 786 8904
Email [EMAIL PROTECTED]

_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to