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 itse
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 a
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.
Actually, I didn't see the
I'm just catching up, and I would agree with David's assessment. If
you go back to the original email and your follow-on one, you will see
that the times listed are all subsecond. If you are noticing DNS
delays, they are probably multi-second, so something else is wrong.
Some snoops might help
I would like to get some questions answered in regards to patching a
zoned Solaris 10 system with a recommended patch cluster and also point
out a problem with the Zones FAQ web page.
In the Zones FAQ (http://www.opensolaris.org/os/community/zones/faq/),
one finds
Q: How do I patch zones?
A:
