Anonymous_User Absent Member.
Absent Member.
1588 views

NW6 NETDB.nlm not resolving using DNS addresses, ok with resolv.cfg

NETDB.nlm is loaded and it does resolve names found in
sys:etc\resolv.cfg
but other domain names are not resolved.

The DNS servers listed in the resolv.cfg ARE valid and there are 2
listed
there.

Example: I try to 'ping abc.com'. The ping screen comes up, it waits
a
second and then says 'could not resolve name ''abc.com''

Any idea what simple thing I am missing here?

Thanks





Labels (1)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: NW6 NETDB.nlm not resolving using DNS addresses, ok with resolv.cfg

Hi,

Phil Hunt wrote:
>
> NETDB.nlm is loaded and it does resolve names found in

sys:etc\resolv.cfg
> but other domain names are not resolved.


Huh? Resolv.cfg doesn't list names to resolve. Resolv.cfg lists your
own
domain name, and the IP addresses of the nameservers.

> The DNS servers listed in the resolv.cfg ARE valid and there are 2

listed
> there.


Please post the resolv.cfg.

> Example: I try to 'ping abc.com'. The ping screen comes up, it

waits a
> second and then says 'could not resolve name ''abc.com''
>
> Any idea what simple thing I am missing here?


It's as simple as the server not being able to resolve that address
via
the configured nameserver listed in resolv.cfg. Either there's a
syntax
error in resolv.cfg, or your server can not reach the listed servers
there.

CU,
--
Massimo Rosen
Novell Support Connection Sysop
No emails please!
http://www.cfc-it.de



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NW6 NETDB.nlm not resolving using DNS addresses, ok with resolv.cfg

OK, you posted essentially the same message in 2 different threads. Please pick one, and let the other one die out... you choose, but
having two conversations about the same thing is way too confusing
here. Please refrain from double-posting in the future. Thanks,

bd
NSC Volunteer SysOp
www.InsightNetSolutions.net




0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NW6 NETDB.nlm not resolving using DNS addresses, ok with resolv.cfg

Sorry, I meant HOSTS, not resolv.cfg

Also, sorry for the double post. I though I had killed this one and
not
sent it.

I now have resolving working. It took a reboot. resolve.cfg does not
take
effect immediately, like the docs say

Phil
"Massimo Rosen" <mrosenno@spamcfc-it.de> wrote in message
news:3FD4A5A7.196E8D61@spamcfc-it.de...
> Hi,
>
> Phil Hunt wrote:
> >
> > NETDB.nlm is loaded and it does resolve names found in

sys:etc\resolv.cfg
> > but other domain names are not resolved.

>
> Huh? Resolv.cfg doesn't list names to resolve. Resolv.cfg lists your

own
> domain name, and the IP addresses of the nameservers.
>
> > The DNS servers listed in the resolv.cfg ARE valid and there are 2


listed
> > there.

>
> Please post the resolv.cfg.
>
> > Example: I try to 'ping abc.com'. The ping screen comes up, it

waits a
> > second and then says 'could not resolve name ''abc.com''
> >
> > Any idea what simple thing I am missing here?

>
> It's as simple as the server not being able to resolve that address

via
> the configured nameserver listed in resolv.cfg. Either there's a

syntax
> error in resolv.cfg, or your server can not reach the listed servers


> there.
>
> CU,
> --
> Massimo Rosen
> Novell Support Connection Sysop
> No emails please!
> http://www.cfc-it.de






0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NW6 NETDB.nlm not resolving using DNS addresses, ok with resolv.cfg


In article <p4mBb.1308$ND5.553@prv-forum2.provo.novell.com>, Phil Hunt
wrote:
> I now have resolving working. It took a reboot. resolve.cfg does

not take
> effect immediately, like the docs say
>

Right. And is that to say that everything is OK on your end now?

bd
NSC Volunteer SysOp
www.InsightNetSolutions.net




0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.