Why is adding a new Ubuntu PC to an existing LAN such a pain?

[Garry Knight]

Derek Broughton wrote:

> Try nslookup or dig.

They return the same 209.123.16.48 address whether my local machine's
host/IP are in /etc/hosts or not.

> You _really_ picked a bad name

Well, you can blame my mother for part of it.  :-)

>  derek at othello:~$ nslookup derek.pointerstop.ca
>  Server:         142.2.13.34
>  Address:        142.2.13.34#53
...
> Note the "Server" line, there.  That's the DNS that returned the address.
> If yours doesn't say 192.168.1.1 there's still a problem in your
> configuration.

No, that part's fine. The router *is* handling the DNS, but as you said,
it's "kicking the problem upstairs".

> Note, with dig you can specify "dig pc.garry.org" and
> "dig pc.garry.org @192.168.1.1", which might potentially show different
> results (indicating that your DNS lookups aren't going to your router -
> though I don't think that's the case).

They both return 209.123.16.48, and they're both showing:
;; SERVER: 192.168.1.1#53(192.168.1.1)

> but have you reconnected that device to the lan since you reset the
> domain? 

I haven't had the time, yet. I'm hoping to be able to take it offline some
time tomorrow.

-- 
Garry Knight
garryknight at gmx.net