I guess if Michelle is using a "small broadband router" like she says, she only has one public IP. So her provider's DNS won't help much to resolve her internal network's client's IPs.
It would of course be better to setup DNS either on the router or on another server in her internal LAN (using her provider's DNS as forwarders), but if it's only to test ssh connectivity and throughput, it will be way easier to just add her client's IP address and name in the resolv.conf file (on the SSH server ). Michelle, please try it. It will always be possible to setup a DNS afterwards and still use dhcp et al. Also, if SSH the connection goes "fast" but tranfers speeds are too slow, you might try using "-c arcfour". I achieve almost 2x throughput with this flag. Please note I don't know about security implications here (and I don't care neither since I use it on a private VLAN, but you might care depending on your situation). -- Arnaud Le 18/02/10 17:33, Leslie H Wood a ?crit : > Pretty sure we are only talking about DNS client here so setup is easy > and I do not see any overhead. At home, see if you can figure out > what your internet provider is supplying. > > 1. If you are using their DHCP then you may have DNS already setup > when the Opensolaris DHCP client connects. If the internet provider > includes DNS records in their DHCP, then DHCP client sets up an > /etc/resolv.conf on Opensolaris. > > If the /etc/resolv.conf exists then test it by "nslookup yahoo.com" > > 2. I have a cable modem and a Linksys router/firewall and I setup a > static IP rather than DHCP from the router. I connected to the > router and figured out my Cable companies DNS IP's and setup my own > /etc/resolv.conf. The man page for resolv.conf is pretty clear. > > domain xx.cox.net > nameserver 68.220.31.11 > nameserver 68.220.32.11 > nameserver 68.220.31.12 > options timeout:3 retrans:3 retry:1 rotate > > I have worked at a big company who used Active Directory for their > naming service and setting the Unix machines /etc/resolv.conf to point > to the appropriate windows servers worked fine. UNIX DNS client > talks to the DNS server process just fine. > > ...Les > > Michelle Knight wrote, On 02/18/10 09:14: >> OK - I'll try this tonight. >> >> I've never bothered with DNS before for the home network and I >> haven't set it up. DHCP is handled by a small broadband router. >> >> If DNS is needed, I'll have to look at setting it on the router and >> putting its IP in the servers DNS tables. >> >> The other thing (which I did do before) was switch off DHCP on the >> router and have the server handle DHCP and DNS ... but it was a bit >> messy for a home network and, to be honest, I've never got the hang >> of setting up DNS properly. >> >> At the moment, DNS is the same as LDAP and advanced permissions the >> name of which escapes me at the moment ... is too heavy for a home >> network. >> >> I have to admit, at work, if the boss wants to attach the V880 and >> the M4000 in to the active directory structure, the shock of the >> request would probably kill me! > > _______________________________________________ > opensolaris-help mailing list > opensolaris-help at opensolaris.org
