dns problem

Hello, i think i have a problem with my dns configuration . I am running Red Hat 9 and there is also apache running on the server. And my apache is running correct i can see my webpages on other machines (clients) in my network, but I can't contact my site from the server on which apache is running. And ofcourse i can see all other pages on the server. I think it's a dns related problem and not a apache one

Is the name server the same as your apache box?
If so modify your /etc/resolv.conf to point to either the ip of the box or localhost.

You're right my nameserver is also my apache box
But applying your solution , as was mentioned in your previous posting, didn't help.
this is how my resolv.conf looks like:
nameserver 192.168.1.1
nameserver 194.134.5.5
nameserver 194.134.0.97
where 192.168.1.1 is my server ofcourse

put only "192.168.1.1" in your resolv.conf. Then setup your DNS server to do "forwarding".
It won't work otherwise.

hth,
M.

whether his DNS server does forwarding or not has no effect on whether either apache or the DNS server provides service locally.

No, but the resolver library configuration does. He cannot have three nameservers in /etc/resolv.conf and expect the system to use another one if one does not have the answer - AFAICS his problem here.

The nameservers in /etc/resolv.conf are expected to deliver the same answers, the system will pick another one in case of failure, not when it gets a negative answer.
Plus, it can depend on circumstances chosen by the OS (see the RFC).

conclusion: use one internal nameserver with forwarding.

hth,
...M

It sounded like to me that you are saying you HAVE to setup BIND to do forwarding in order to locally access the webserver. I was disagreeing. I can go into why if you really do think you have to setup BIND to use forwarding to locally access the webserver.

I think he could need forwarding since he had some public DNS servers in his resolv.conf ... you know, preventing his next question "Now the internal server works, but I can't connect to the internet anymore..."

...M

ah. well. You don't need forwarding to have BIND resolve queries for domains not hosted by its server. It will just have to start at the root servers and resolve the domains itself. The better option is to use the ISP provided caching dns servers as the target of forwarding, but forwarding is never required to make things work. The only exception I can think of is if an internal dns server does not have direct access to the internet and must be told to forward to a gateway dns server.

Now I can see it too... When talking to people, I usually refer to using a cache zone as "forwarding" too because that's what it does...
"forwarding" is a bad choice of wording, my fault.

M

Guys I tried all the above solutions mentioned in the previous postings , as far as i could understand it. But it still doesn't work, what should i do according to the postings of Hirsch and Silent Rage, can somebody summarize it ?

Summary:

Where "forwarding" is either
- using a cache zone (the one called "." with the "root.hints" file)
- or using the "forwarders" option of bind (put the name server IPs that you removed from your resolv.conf there as forwarders, this is the recommended way).

If the "forwarders" option of bind does not work for you:
- maybe your provider blocks you from using his DNS as forwarders (probably by accident)
- use the "query source" option of bind specifying your official IP as source
- use the "query source" option to specify a port > 1024 so the other end cannot tell that you are doing forwarding (untested, not 100% on that)

If the "root.hints" zone does not work, update the file. iirc some of the root servers changed their IPs recently or something (not sure, but this helped a friend of mine, his default file from a bind installation was from around 1997)

... And it would help alot if you told what "does not work" means for you We need some lines from your log file, feed us please...

hth,
M.

First of all i like to thank everybody whose helping me out. What i mean with " it's not working" i have a apache webserver running on the same machine as my DNS server. I can get any page from the internet on my machine, except my own webpage. My resolve.conf reads :
domain bahadoer.homelinux.com
search bahadoer.homelinux.com
nameserver 192.168.1.1
You asked me for logfiles, but where does named put it's log files.

/me is reminded of the SNL show where the nerds are like "MOVE!" to fix the employee's computer themself