Can't resolve hostname

[optimised]

Hi,
From a remote pc I can only get to the apache test page using my dns servers ip address. When trying to get

http://www.address

I get no server find.
Just wondering If I'm missing something. This is a continuation to thread below 'access by ip only'

These are the configurations I guessing may be contributing to the problem.

//Host file
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
172.25.47.98 ns1.mydomain.com mydomainNS
172.25.47.98 mydoamin.com mydomain

//resolve.conf
search mydomain.com
nameserver ip one of isp nameserver
nameserver ip two of isp nameserver


What should be in this file?
/etc/nsswitch.conf
Is this correct?
"hosts: dns files"

//host.conf
order hosts,bind
multi on #should I add this line


Thanks

 

[StarTAC]

have u setup your /etc/httpd/httpd.conf file correctly, to reply to requests whose header is

http://www.youraddress.com...

that should be the problem...

have the same

http://www name

in mapping to the web server's IP address in your DNS server.. or the one authoritative for your domain...

good luck

 

[optimised]

Hi StarTAC,

I assume that you are referring to virtualhosting.
Is there somewhere else in the httpd I need to make changes?
I'm thinking the same thing it is in my httpd file. I can't
quite put a finger on what's wrong. At first I was thinking that there may be a firewall on port 53 but there isn't. What makes me think something, somewhere is not configured properly is because I can ping and ftp to ip address but not domain, but if I'm getting my apache test page using my servers ip address does this mean my dns is running properly
and the httpd.conf is at fault?


//httpd vhost section
NameVirtualHost 172.25.47.98

<VirtualHost 172.25.47.98>
Servername

http://www.mydomain.com

DocumentRoot /home/domain/www
</VirtualHost>


thks

 

[stanhubble]

are these configurations from the server or the remote pc? It sounds more like the problem is the resolution of name -> ip on the remote pc, not the server

 

[optimised]

Hi,
I'm thinking that because my isp provided me with the info on my ip addresses as :172.x.x.x maps to 205.x.x.x I had to use the 172. numbers on the eth0 config to have internet connection the 205. numbers won't give me internet connection.
My isp tells my that buy being able to pull up my website at my ns1 ip address, the problems on my side.
I believe that NAT is causing the problem that my server can't be found, as I said before I'm able to ping and ftp to my ip but I cannot ping domain/host. I'm not sure but to me it seems the 205. number on there router Must be on my phyisical machine.

just a thought

 

[StarTAC]

if u are able to ping and ftp into the server using IP.. then the only reason u can't do it with the domain name is that there's no DNS forwarding going on.. what u need to do is ensure your resolver is working okay.. and also test the DNS configuration of the DNS server authoritative for your domain.. or at least the one u are using in your resolver... try doing an nslookup of other servers from that DNS server.. then ping the domain of your box using that DNS server.. that would be a good start..

good luck...