host unresolvable

Hi,

little confused and I must say that is one fine manual
but stuck on when I dial up and connect then I go to
dial in an address an it will not resolve stating that the host is unknown. I'm not so sharp with DNS and when I look at my slak /etc/resolv.conf it looks

#xxx.xxx.xxx.xxx
#xxx.xxx.xxx.xxx

2 ips but are commented out? helplease!

Thanx

Should you get nameservers from DHCP servers with bad nameservers or comment out from your ISP which overwrite your /etc/resolv.conf when you get connected, just write a script and uncomment them or contact your ISP.

Are you sure this is more of a BSD question?

In slackware when i connect the resolv.conf has a temp entry written

and I just installed freebsd4.3 and I can connect to the net but hosts are unresolvable by name i'ma try ip

originally in bsd there was no resolv.conf
so i make one with read all write too group wheel?

and slak has root.root user write??

forced to learn

I try ip address and it will find the site but won't connect it will prompt me with the domain name and tell me unknown nost even though it tells me who it is

216.254.XXX.XXX remote ip
216.254.xxx.xxx local ip

also the ppp will say

105.103.8.8 for both remoteand local?

>> so i make one with read all write too group wheel?

Just keep the default owner/group as is. Default to -rw-r--r-- (644).

>> and slak has root.root user write??

So? slack is not BSD. If you like seeing a root group, go back to Linux.

>> I try ip address and it will find the site but won't connect

How? Which protocol?

>> 216.254.XXX.XXX remote ip

If you want us to test that site for you, provide us the real IP. Why you need to hide it at all?

sorry but

i don't have a site the ip's are dynamic 216.254.xxx.xxx (isp)

for me dialing up to the net and it connects @ above addr

then I could try say devsheds ip http://ip.x.x

it prompts me http://www.devshed.com host unknown

I don't know whats wrong so its hard too explain

thanx anyway

>> i don't have a site the ip's are dynamic 216.254.xxx.xxx (isp)

What? I thought that was the IP you tried to initialize a connection to? Now that you are telling me what was the IP randomly assigned to you by your ISP. Sorry I am lost.

>> I don't know whats wrong so its hard too explain

Please explain a little bit better so I or someone else can understand your problems.

from start
kde
kppp--click on it ---- warning: /etc/resolv.conf not found

I create a blank one
I hit connect it connects to my isp 216.254.xxx.xxx
my local addr now is 216.254.xxx.xxx

I'm on the net the names for sites will not resolve

ie; http://devshed.com rompt host unknown

in my resolv.conf there is no temp entry for nameservers like other os

going in now to try placing ns ips there

this is real basic i'm just real stupid

Okay, now that I know it's a dhclient problem. Here are some questions for you:

1) Do you know the nameserver IPs of your ISP?
2) In Windows, can you surf the web and resolve hostname to IP when you choose Optain IP Automatically and under DNS tab your nameserver field is left blank with no entry?

Most ISPs assign nameserver to client automatically when using DHCP. If you know your ISP do that, your /etc/resolv.conf will be overwritten once connected.
If they don't, you can manually append the nameserver IPs (you need to ask your ISP) to your /etc/dhclient.conf file like so:

prepend {
domain-name-servers 12.34.56.78;
domain-name-servers 12.34.56.79;
}

I don't use DHCP so I can't help you much on this. Why don't you check FreeBSD handbook or search about the syntax of dhclient.conf?

okay got it

I staticed the primary and secondary in the
resolv as you said

thing was in lin it would write auto
so I took the scenic route

thank alot bsd this stuff is awesome

recommends
apache
zope
aol

Bob, I just tried to post a reply to your tree sync thread but it was deleted. Here is my reply:

>> how to get my ports synced with cvs

You first need to track -STABLE branch. Since you have never recompiled a kernel, apparently you are not running -STABLE and you shouldn't cvsup your ports tree in the first place.

>> also when is the best time to compile kernel

Before installing any packages or ports.

>> got my cvsupdating

You can quit that now, don't waste your time any further. As I said, FreeBSD users running, say 4.4-RELEASE, can cvsup their ports tree but can't make install particular software because latest ports collection is for users who track -STABLE. Though there is a way for -RELEASE users to cvsup and update to the latest ports collection but I don't recommend that unclean way of doing things in FreeBSD.

What you should do now:
1) quit cvsup your ports
2) rm -rf /usr/ports
3) reinstall original ports from CD
4) cvsup upgrade to 4.4-STABLE (as of today it should be 4.5-PRERELEASE)
5) recompile a kernel (this alone gives you alot to mess around with)
6) cvsup your ports

Keep in mind, 4.5-PRERELASE is in beta stage (not so stable). Should you try track -STABLE at this time, you'd better off just wait another month or so to make your life easier.

yeah i thought maybe the update would
solve my problem but it didn't

so that sounds good I will do all that
I guess i want the stable-supfile?

so if I track 4.4
It is no prob to sup to 4.5 and ports
when stable

Again thanks alot

>> I guess i want the stable-supfile?

Yes and like this:

/usr/local/etc/cvsup/src-supfile

*default host=cvsup8.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=RELENG_4
*default delete use-rel-suffix
*default compress
src-all

>> It is no prob to sup to 4.5 and ports

Once you are at 4.5-PRERELEASE, you can cvsup your ports. When 4.5-STABLE is out, cvsup your src again (this time the src has minimal change, buildworld should be easier).

cd /usr/src/sys/i386/conf

config MEKERNEL


ERROR: version of config(8) does not match kernel!
config version = 400018, version required = 400019

Make sure that /usr/src/usr.sbin/config is in sync
with your /usr/src/sys and install a new config binary
before trying this again.

If running the new config fails check your config
file against the GENERIC or LINT config files for
changes in config syntax, or option/device naming
conventions

My searches have returned nada clue
on (5 )all previous done in step

assume this is not to big a deal so will proceed to make

# make depend

make: don't know how to make ../../conf/param.c. Stop


?huh?

it worked b4