Need help with DNS setup

[hotdrew24]

I'm running a redhat linux 9.0 for a webserver, and I'm confused as to how BIND should be setup. It is somewhat setup as of now using the GUI setup, but my problem is that

http://server1.mydomain.com

works but

http://mydomain.com

doesn't work. Does this pop a solution to anyone? I'm very new at linux sys as well as webhosting.. I have gone through different manuals, but can't figure out the BIND setup. Please help? and please be specific since I'm so noob at this stuff.. Thank you.

Sincerely,
Andy

 

[Serbtastic]

Try pinging mydomain.com and see if it resolves to an IP address.

 

[hotdrew24]

I tried pinging mydomain.com but get "could not find host" reply. But here's the thing. I had server1.mydomain.com, ns1.pbi.net, and ns2.pbi.net as nameservers when I registered my domain with my registrar. ns1&2.pbi.net was provided by my ISP with instructions to run a reverse in-addr zone. So, what I did yesterday was to delete server1.mydomain.com from my registrar record and leave only ns1.pbi.net and ns2.pbi.net. Now, server1.mydomain.com doesn't work either, which leads for me to believe that my ISP screwed up somehow, right? I think I did all they asked me to do correctly. Well, what do you think? and thank you so much for your response. I would greatly appreciate another one.
sincerely,
Andy

 

[andybthegeek]

you need to add yourdomain.com to your /var/named/

http://www.yourdomain.db

/var/named/

http://www.yourdomain.com.zone

depending on how your files are named. for example:

$TTL 86400
@ IN SOA

http://www.yourdomain.net.

root.localhost (
2 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttl
)

IN NS ns.yourdomain.net.

fabio IN A 192.168.2.2
phil IN A 192.168.2.3
bob IN A 192.168.2.4
ns IN A 192.168.2.1
@ IN A 192.168.2.1


depending on you version of bind you should be able to use the '@' to indicate

http://www.yourdomain.net

for another example

$TTL 3h
yourdomain.net IN SOA server.krikkit. root.localhost. (
1999100502 ; serial
28800 ; refresh
14400 ; retry
3600000 ; expire
86400 ; default_ttl
)
yourdomain.net IN NS ns.yourdomain.net
localhost.yourdomain.net IN A 127.0.0.1
ns.yourdomain.net IN A 192.168.0.1
bob.yourdomain.net IN A 192.168.0.1
tom.yourdomain.net IN A 192.168.0.5
marvin.yourdomain.net IN A 192.168.0.6
hal.yourdomain.net IN A 192.168.0.7

best luck

andy

 

[Freemansweb]

yourdomain.net IN NS ns.yourdomain.net
localhost.yourdomain.net IN A 127.0.0.1
ns.yourdomain.net IN A 192.168.0.1
bob.yourdomain.net IN A 192.168.0.1
tom.yourdomain.net IN A 192.168.0.5
marvin.yourdomain.net IN A 192.168.0.6
hal.yourdomain.net IN A 192.168.0.

The example shows 127.x and 192.x addresses. These are localhost and network addresses. I don't think those addresses will work for actual internet access. I realize this is an example, but it could be misleading.

http://fwwebs.com