I installed RH 9 last night. I custom installed many server components, including the DNS server, but it isn't configured yet.

I finished install, set up the NIC card and fired up Mozilla. I couldn't surf to ANY SITES using a DNS naming convention.

XXX.redhat.com --> barfed, (won't post this as a url)
BUT
66.187.232.56 --> WORKED...WTF

I don't get it...WHY is it working one way but not the other.

Thanks...

P.S. That is the most STOOOOOOPID restriction I HAVE EVER SEEN...restricting URL posting ....

Check your /etc/resolv.conf file to see what nameserver you have listed. If you DNS server is working then you should be able to use:
nameserver 127.0.0.1 (if you are listening on loopback)

Also, to check to see if your DNS server is resolving try using nslookup and point to your server
nslookup
server 127.0.0.1
www.redhat.com

If it resolves, then your DNS server is working.

YOU DON'T WANT YOUR MACHINE TO BE A DNS SERVER - YOUR ISP PROVIDES THAT

That is not necessarily true. I run an internal DNS server because my mail server requires internal lookup and I can put my own entries in for my internal domain. There ARE reasons why you would want to run a DNS server. Also, you could run a caching DNS server to speed up lookups. Just because your ISP provides one doesn't mean you shouldn't. Let him decide.

YOUR RIGHT, BUT HE IS NOT RUNNING A LAN, HE DOESN'T REQUIRE IT FOR INTERNET ACCESS

I installed the DNS component because I was considering setting the DNS server for my Website.

My DNS does have a LOCALDOMAIN.LOCALHOST defined, but I will check the /etc/resolv.conf file when I get home.




BUT, I am still fighting with my DLINK router. I can see my website from the LAN but the WAN won't let any requests in. Anyone have a good link to a dlink & Linux Webserver set up page?


Thanks for the help

Frog

I run a linux webserver/DNS/DHCP/NTP/SAMBA server behind a D-Link router. I haven't had any problem. Which D-link do you have. I had DI-704 then switched to DI-614+, which I have had some trouble with DNS. Other than that it works fine. Just point port 80 and 53 to your internal box. It should work fine.

I have the Di-614+ also.

Did you set the virtual server or the Firewall ?

I was using the firewall
SOURCE=WAN
IP Range Start=192.168.0.1
DESTINATION=LAN
IP RANGE = 192.168.0.100 ( this is my LINUX Box )
Protocol=TCP
PORT Range= 80

I also did this for VIRTUAL SERVER and I can ping my Linux box from outside, I can see my site from the Winbox on the LAN,
BUT I Can't get the WAN to let the incoming requests in.

I didn't use PORT 53 tho'. Do you have a suggestions.

Thanks,
Frog

P.S. What are your Samba settings, I was going to get that re-configured next.

Regarding MY DNS loopback problem.

I nslookup 127.0.0.1 and get CONNECTION TIMED OUT; no servers could be reached.

BUT... I checked my services and my NAMED (bind) wasn't live.

Once started my DNS resolution is working...hurrah


Frog

Here are global configs:
# Global parameters
[global]
workgroup = INSIDE
netbios name = SUSEY2
interfaces = 192.168.0.10
encrypt passwords = Yes
map to guest = Bad User
username map = /etc/samba/smbusers
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
character set = ISO8859-15
os level = 2
printing = lprng
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
wins support = yes
dns proxy = no
syslog = 0
log file = /var/log/samba/smb.log
debug timestamp = yes
max log size = 50

Then setup your shares as you like them.

>BUT, I am still fighting with my DLINK router. I can see my >website from the LAN but the WAN won't let any requests in. >Anyone have a good link to a dlink & Linux Webserver set up >page?

I had the same problem! Until i noticed that the ports assigned in DI-604s virtual server was assigned to 2 computers in the netw.

I changed it to only be assigned to 1 ip and after that everything worked perfect.

Try using your wan ip as the url

http://youripaddress

and see if that works.

Secondly if your web page wants to be seen from the internet out, you need to buy the domain, and setup a name server with your dns server being the host of the ns's.

Most importantly disable the firewall on the apache server, since you have a router between it and the outside world.