 | | (canceled) —Jamie Obrien
|
| | | |
| | | | | Re: Networking Round 2 —Dan Boger
|
| | | | (...) hmmm.... looks like named couldn't bind to port 53 - is there anything else bound to that port? perhaps inet or some other named proccess? Dan (24 years ago, 19-Mar-01, to lugnet.off-topic.geek)
|
| | | | |
| | | | | | (canceled) —Jamie Obrien
|
| | | | |
| | | | | | Re: Networking Round 2 —John D. Forinash
|
| | | | | (...) This may be a stupid question, but you didn't mention it: do you have your /etc/resolv.conf pointing in the right place? -JDF (24 years ago, 20-Mar-01, to lugnet.off-topic.geek)
|
| | | | | |
| | | | | | | (canceled) —Jamie Obrien
|
| | | | | | |
| | | | | | Re: Networking Round 2 —John D. Forinash
|
| | | | (...) Oh! Another thing: I wouldn't use local.com unless you actually own local.com and the root nameservers point to you to resolve local.com. But I don't _think_ that's what's causing your problem. I'd use something with a domain that doesn't (...) (24 years ago, 20-Mar-01, to lugnet.off-topic.geek)
|
| | | | |
| | | | | | Re: Networking Round 2 —Matthew Miller
|
| | | | (...) Yeah just you wait 'til they open up new TLDs; if it's done right, .foo will be one of the first to go. (And then .bar, of course....) (24 years ago, 24-Mar-01, to lugnet.off-topic.geek)
|
| | | | |
