again DHCP !?!?

Actaully /etc/resolv.conf is being set up with nameservers ( DNS ) provided
by the DHCP server. It is made automatically after dhcp.client has been
started.
Although when I " ping kvardin" or somebody else who I know it is not
resolved --"Unknown host ".
So what is the catch ?!?!
Here is how I start dhcp.client :
#dhcp.client -ien1 -hkvardin&
After that I am able to ping absolute addresses, I am also browsing,
telneting,…, but not name resolving !!
Regards !
Kostadin Vardin

“Kostadin Vardin” <kvardin@primus.ca> wrote in message
news:a6qsg9$lo8$1@inn.qnx.com

Actaully /etc/resolv.conf is being set up with nameservers ( DNS )
provided
by the DHCP server. It is made automatically after dhcp.client has been
started.

DNS and DHCP server are two disctint entity. When a new machine is
detected by the DHCP server, the entries of the new machine isn’t
automaticaly added in the DNS. Some DNS server (Microsft)
can deal with this but most don’t. Even the Microsoft one needs
some fiddling, I’m told.


Although when I " ping kvardin" or somebody else who I know it is not
resolved --"Unknown host ".
So what is the catch ?!?!
Here is how I start dhcp.client :
#dhcp.client -ien1 -hkvardin&
After that I am able to ping absolute addresses, I am also browsing,
telneting,…, but not name resolving !!
Regards !
Kostadin Vardin
\

“Mario Charest” <goto@nothingness.com> wrote in
news:a6r4h3$r1s$1@inn.qnx.com:

“Kostadin Vardin” <> kvardin@primus.ca> > wrote in message
news:a6qsg9$lo8$> 1@inn.qnx.com> …
Actaully /etc/resolv.conf is being set up with nameservers ( DNS )
provided by the DHCP server. It is made automatically after dhcp.client
has been started.

Do a getconf _CS_RESOLVE and see if the name server info is there - my bet
is that it isn’t. Instead of using dhcp.client manually, what happens if
you use the GUI tool to configure your network via DHCP
(/usr/photon/bin/phlip - login as root to run (su -)).

\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

“Adam Mallory” <amallory@qnx.com> wrote in message
news:Xns91D264DD9800Camalloryqnxcom@209.226.137.4

“Mario Charest” <> goto@nothingness.com> > wrote in
news:a6r4h3$r1s$> 1@inn.qnx.com> :


“Kostadin Vardin” <> kvardin@primus.ca> > wrote in message
news:a6qsg9$lo8$> 1@inn.qnx.com> …
Actaully /etc/resolv.conf is being set up with nameservers ( DNS )
provided by the DHCP server. It is made automatically after dhcp.client
has been started.

It doesn’t make any difference, the DNS doesn’t learn about the new machine.
If you go look at the DNS database I’m sure you’ll see the entry for the new
machine isn’t there.

Thanks for your commitment guys,
Here is the result of getconf _CS_RESOLVE:
nameserver_207.181.101.4
nameserver_207.181.101.5
nameserver_10.0.0.1

The same is also written automatically into /etc/resolv.conf after
dhcp.client returns.
I am expecting the answer of our sysadmin regarding DHCP server <-> DNS
cooperation as it seems this might be the explanation.
Regarding the docs dhcp.client is setting enviroment vars like IPADDRESS,
NAMESERVER1, NAMESERVER2, HOSTNAME … and submits them to /etc/dhcp/dhcp-up
script if such exists. I created such a script just to echo for myself the
results of dhcp.client, but it is not even called form dhcp.client as
expected. I think this scripts is very usefull at least to detect some
anomalies into DHCP server <-> DNS.
Regards !
Kostadin Vardin


“Mario Charest” <goto@nothingness.com> wrote in message
news:a6t5d9$cso$1@inn.qnx.com

“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:Xns91D264DD9800Camalloryqnxcom@209.226.137.4
“Mario Charest” <> goto@nothingness.com> > wrote in
news:a6r4h3$r1s$> 1@inn.qnx.com> :


“Kostadin Vardin” <> kvardin@primus.ca> > wrote in message
news:a6qsg9$lo8$> 1@inn.qnx.com> …
Actaully /etc/resolv.conf is being set up with nameservers ( DNS )
provided by the DHCP server. It is made automatically after
dhcp.client
has been started.

It doesn’t make any difference, the DNS doesn’t learn about the new
machine.
If you go look at the DNS database I’m sure you’ll see the entry for the
new
machine isn’t there.

Well,
The problem explanation ( as I was told by our sysadmin) is that our DHCP
server does not log hostnames into the local name server, actually it is
used WINS!
Regards !
Kostadin



“Kostadin Vardin” <kvardin@primus.ca> wrote in message
news:a6t839$eso$1@inn.qnx.com

Thanks for your commitment guys,
Here is the result of getconf _CS_RESOLVE:
nameserver_207.181.101.4
nameserver_207.181.101.5
nameserver_10.0.0.1

The same is also written automatically into /etc/resolv.conf after
dhcp.client returns.
I am expecting the answer of our sysadmin regarding DHCP server <-> DNS
cooperation as it seems this might be the explanation.
Regarding the docs dhcp.client is setting enviroment vars like IPADDRESS,
NAMESERVER1, NAMESERVER2, HOSTNAME … and submits them to
/etc/dhcp/dhcp-up
script if such exists. I created such a script just to echo for myself the
results of dhcp.client, but it is not even called form dhcp.client as
expected. I think this scripts is very usefull at least to detect some
anomalies into DHCP server <-> DNS.
Regards !
Kostadin Vardin


“Mario Charest” <> goto@nothingness.com> > wrote in message
news:a6t5d9$cso$> 1@inn.qnx.com> …

“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:Xns91D264DD9800Camalloryqnxcom@209.226.137.4
“Mario Charest” <> goto@nothingness.com> > wrote in
news:a6r4h3$r1s$> 1@inn.qnx.com> :


“Kostadin Vardin” <> kvardin@primus.ca> > wrote in message
news:a6qsg9$lo8$> 1@inn.qnx.com> …
Actaully /etc/resolv.conf is being set up with nameservers ( DNS )
provided by the DHCP server. It is made automatically after
dhcp.client
has been started.

It doesn’t make any difference, the DNS doesn’t learn about the new
machine.
If you go look at the DNS database I’m sure you’ll see the entry for the
new
machine isn’t there.
\

“Kostadin Vardin” <kvardin@primus.ca> wrote in
news:a6tef0$j4d$1@inn.qnx.com:

Well,
The problem explanation ( as I was told by our sysadmin) is that our
DHCP server does not log hostnames into the local name server, actually
it is used WINS!
Regards !
Kostadin

Thanks for the info Kostadin!


\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>