www before domain just stopped working

r3n3gad3

Verified User
Joined
Aug 11, 2004
Messages
19
Hi,

I've been scripting the whole day on my website in php and al a sudden the www address stopped working, the address like 'domain.com' works perfectly but if I go to 'www.domain.com' the domain wont load and gives a time-out, how can this be?

the DNS management shows this:
domain.com. A *.*.*.104
ftp A *.*.*.104
localhost A 127.0.0.1
mail A *.*.*.104
pop A *.*.*.104
www A *.*.*.104
domain.com. NS ns1.domain.com.
domain.com. NS ns2.domain.com.
mail MX 10
domain.com. TXT "v=spf1 a mx ip4:*.*.*.104 ?all"

ftp, mail etc works also perfectly... the only thing is that the www wont work? :confused:
 
Use a site like network-tools.com to check to see if the hostname is resolving.

Restart the named program and look in /var/log/messages for errors
 
nothing strange there:

Jul 16 16:29:17 Server001 named[3680]: shutting down
Jul 16 16:29:17 Server001 named[3680]: stopping command channel on 127.0.0.1#953
Jul 16 16:29:17 Server001 named[3680]: stopping command channel on ::1#953
Jul 16 16:29:17 Server001 named[3680]: no longer listening on 127.0.0.1#53
Jul 16 16:29:17 Server001 named[3680]: no longer listening on *.*.*.104#53
Jul 16 16:29:17 Server001 named[3680]: no longer listening on *.*.*.103#53
Jul 16 16:29:17 Server001 named[3680]: no longer listening on *.*.*.105#53
Jul 16 16:29:17 Server001 named[3680]: exiting
Jul 16 16:29:17 Server001 named: named shutdown succeeded
Jul 16 16:29:17 Server001 named[3932]: starting BIND 9.2.4 -u named
Jul 16 16:29:17 Server001 named[3932]: using 2 CPUs
Jul 16 16:29:17 Server001 named[3932]: loading configuration from '/etc/named.conf'
Jul 16 16:29:17 Server001 named[3932]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 16 16:29:17 Server001 named[3932]: listening on IPv4 interface eth0, *.*.*.104#53
Jul 16 16:29:17 Server001 named[3932]: listening on IPv4 interface eth0:0, *.*.*.103#53
Jul 16 16:29:17 Server001 named[3932]: listening on IPv4 interface eth0:1, *.*.*.105#53
Jul 16 16:29:17 Server001 named[3932]: command channel listening on 127.0.0.1#953
Jul 16 16:29:17 Server001 named[3932]: command channel listening on ::1#953
Jul 16 16:29:17 Server001 named[3932]: zone domain.com/IN: loaded serial 2006071600
Jul 16 16:29:17 Server001 named[3932]: running
Jul 16 16:29:17 Server001 named[3932]: zone domain.com/IN: sending notifies (serial 2006071600)
Jul 16 16:29:17 Server001 named[3932]: received notify for zone 'domain.com'
Jul 16 16:29:17 Server001 named: named startup succeeded
 
Working now:

just change some settings in my DNS:

*.pigfarm.com A 22.23.24.25
pigfarm.com. A 22.23.24.25
ftp A 22.23.24.25
localhost A 127.0.0.1
mail A 22.23.24.25
ns1 A 22.23.24.24
ns2 A 22.23.24.26
pop A 22.23.24.25
www A 22.23.24.25
pigfarm.com. NS ns1.pigfarm.com.
pigfarm.com. NS ns2.pigfarm.com.
mail MX 10
25.24.23.22.in-addr.arpa. PTR pigfarm.com.
25.24.23.22.in-addr.arpa. PTR ns1.pigfarm.com.
25.24.23.22.in-addr.arpa. PTR ns2.pigfarm.com.
pigfarm.com. TXT "v=spf1 a mx ip4:22.23.24.25 ?all"

The only thing now is that the wildcard dns doesn't works yet....
 
Back
Top