-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For offices I generally use their actual domain, but I create a subdomain such as lan or office. For me personally I used one of the domains that seemed most appropriate, and and used the lan subdomain.
So, my router is border.lan.meganerd.ca. All internal hosts have forward and reverse dns set up (so a who command will show the fqdn of the host I am logged in from). There is nothing wrong with not following the domain.tld but it is easier to miss errors, which may show up in odd places (smtp servers for example, or reverse proxies). Besides it makes it easier to implement in production. If you don't have a domain just use .local instead of .com, .ca etc. This is the MS default on later version of their server software (broken DNS is usually the root of many AD problems that I encounter. I do not make money from O'Reilly, but their DNS/Bind book is fantastic regardless of your platform. For a cheaper and more instant alternative the following links are a pretty good start: http://www.tldp.org/HOWTO/DNS-HOWTO-2.html http://www.tldp.org/HOWTO/DNS-HOWTO-9.html For a windows network, if you are using Active Directory, DNS is already configured, though likely broken if there are no fqdns in the lan. Have fun cleaning that up. Cheers, Tek Budda wrote: > Shawn wrote: > >>Yep, I have a similar set up myself. When I add a new computer, or virtual >>host (via Apache), I just add an A record to the config file for my domain, >>and restart the service. >> >>For instance, my old server's name was "srv". I am able to do "ping srv", >>and >>it resolves to the right internal IP address, which means I can also do >>"http://srv"; in a web browser on the network. >> >>If you want I can send you my config file as a sample.... > > > Could you send me a copy as well Shawn? I would be interested in doing > something similar. Am actually thinking of it for work as well. Yes it > will likely be on IIS, but the concepts should be the same. > > Cameron > > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDvhQCwRXgH3rKGfMRApawAJ92vB9S85eDkY6EWO52BwDNS9dsRwCggurY bx73UyGGz+JRTgghJD81Fow= =ATVl -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
