Home routers often act as a DNS relay. When DNS relaying is enabled the systems on the private network that are configured via DHCP will have their dns address set to the IP of the gateway/router. The router then forwards requests to the actual DNS address on the WAN side of the router and caches the result for faster NS lookups in the future. When I mentioned dynamic dns before, what I was referring to is a feature where the router automatically notifies a server what the ip address you are currently assigned is. This server provides a vanity address that can be used to access your lan from the net. Essentially you get a static 'named' address that will always point to your dynamically changing ip address. Check out http://www.technopagan.org/dynamic/ -Tharin O.
DHSinclair <[EMAIL PROTECTED]> wrote: inline below...... At 21:32 11/09/2007 -0800, Tharin O. wrote: Most of the modems provided by the two telcos in my area, ATT and Verizon, seem to come in one of two designs. A single ethernet and/or usb port DSL modem intended for use with one PC or a router. The other a combination of a dsl modem, router, switch, and wireless ap. Yes, I have the "single" design. There is one input for the phone line, and only 1 (wan?) output for the "router" line. (odd that they call this a router with only 1 port, but I'm still learning). Very odd modem, but that is just my comment. Open to comments(?) I can play ethernet or USB, but not both together. I am doing straight ethernet. An http interface is used to change the settings of modem and maybe look at the stats of the dsl signal. Check! Yes. That is true, once you figure out how to get "at it!." Got it. Many thanks to your stellar explanations. (I gave up the older telnet interface in 2000. Though, I do still know how to play that way too.) It was (is) on HTTP that my modem would not answer the "htt?://launchmodem" entry in the browser. The modem DID answer the more 'direct' request of "htt?://192.168.1.254". I do understand this. Now. Different levels of 'ask.' (in my terms). Got there. The modem is now "bridged ethernet." If you have your own router I've found it to be better to disable PPPoE on the modem and switch it to a bridged mode. It's much easier to start and tear down the pppoe sessions from your router instead of the modem. If you use the dynamic dns service in the router it will be better at issuing updates as well. OK. I have the modem 'bridged ethernet' but have not figured out how to kill PPPoE yet. I suppose that 'PPPoE' might be disabled at this point. Perhaps not. For the last 20 hours, it seems that the router is latching up to the modem very quickly (using PPPoE) in an /on demand/ situation. (This I can change just as soon as I find the switch in the router.) Now, I am not certain this is necessary. (another entire topic!). Yes, the router is still set to /on demand/. Still thinking about this. OK. Now we are back to either non-dynamic or dynamic DNS. I do use the DNS servers of BellSouth (where I am). Yes, they are NOT on my local (private) network. Just where, do these DNS addresses need to be? Yes, I have not elevated my server to a domain controller yet. Sorry, Greg. Still thinking.
