DNS resolution Redhat 8.0

I am new to using Linux from home with dialup access, I have used it successfully on an office network. However I am trying to convert from Windows 2000 to Linux and have setup my machine with dual booting. I have configured the modem for dialup and can connect to my ISP. However I cannot ping URLs I can only ping the IP-address. I have added the DNS entries and have tried setting the dynamic DNS setting on and off, however I cannot seem to get this to work.

Am I looking in the wrong place and setting the wrong thing? My /etc/hosts and /etc/resolv.conf look fine. Is there a background process I should verify is running? I really want to move off of Windows but cannot until I resolve this.

I appreciate any help you can provide.

Aldo

probably a routing problem. can u ping your ISP's DNS servers?

Once connected, run this:

route -n

and verify that ur default gateway is the IP address from your ISP.

I can ping the DNS address provided by my ISP no problem, the address is 204.119.56.2 (they gave me two, but I only pinged the one).

I have tried this with the flag for 'Automatically obtain DNS information from provider on' checked and unchecked with the same result.

The route -n returns the same result as well, the output follows:

Destination Gateway Genmask Flags Metric Ref Use Iface
216.239.168.224 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 216.239.169.224 0.0.0.0 UG 0 0 0 ppp0

Sorry the spacing is a little off on this email. Strange the address 216.239.168.224 is not what I expected to see.

Still confused on this end?

aldo

Try something like this: "nslookup www.linuxquestions.org 204.119.56.2"

For me, this returns:

Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server: 204.119.56.2
Address: 204.119.56.2#53

Name: www.linuxquestions.org
Address: 64.179.4.146

and/or this: "nslookup 64.179.4.146 204.119.56.2"

For which I get returned:

Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server: 204.119.56.2
Address: 204.119.56.2#53

146.4.179.64.in-addr.arpa name = linuxquestions.org.

Therefore, I know your nameserver works. Does it give you the same information?

(Aside: Hey, I grew up with nslookup, so it works for me. Does that mean I am to be depreciated?)

When I execute the nslookup I get the following:

Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.

;; connection timed out; no servers could be reached

Looks as though the nameserver is not working. I tried this with each to the addresses as you suggested.

So whats next?

(If you can figure this out your are certainly not deprecated in my book! [Had to look it up in the dictionary to know what it meant ;-)] )

Originally posted by aldo When I execute the nslookup I get the following: Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing. ;; connection timed out; no servers could be reached Looks as though the nameserver is not working. I tried this with each to the addresses as you suggested. So whats next? (If you can figure this out your are certainly not deprecated in my book! [Had to look it up in the dictionary to know what it meant ;-)] )

Iam also facing the same problem. I didn;t see any replies to this.

If I execute host -T yahoo.com, it resolves the IP address though.

$ host -T yahoo.com
yahoo.com has address 66.218.71.198

I have seen someone post something (somewhere else on this site) that said they had the same problem (dig <doesn't work> and dig -T <works>) and it was solved with a security change - search this forum for
"no servers could be reached" or "dig -T"

- MattFatt