sina

Active Member
Mar 7, 2002
38
0
306
One of our resellers main sites is down. Not pingable or anything. The nameservers have not been changed nor the domain has expired.

All its client sites do work properly and his main site is also in the httpd.conf !!

What could be the issue ?

Thank you very much for any help !
 

dandanfireman

Well-Known Member
PartnerNOC
May 31, 2002
117
0
316
Curious issue. My first inclination would be to verify that name resolution is correct.

You said that you could not ping it.

Ping it by name: ping www.resellerdomain.com
see what IP address it actually tries to ping
Does this address agree with what it should be?
 

sina

Active Member
Mar 7, 2002
38
0
306
Its not pingable, it wont fine the host !!

Ping request could not find host *****.com. Please check the name and try again.

? ? ? ?
 

feanor

Well-Known Member
Aug 13, 2001
835
0
316
The domain's authoratative nameservers are the same server as the webserver in question here, right?

As root logged into the machine, can you do an nslookup on localhost for the domain that is not responding? Does the nameserver give you the proper information?

If not check /var/log/messages for why that particular zone dropped out of warp.
 

sina

Active Member
Mar 7, 2002
38
0
306
Feanor thanks for the reply,

server can't find ******.com: SERVFAIL

The nslookup does not find the host ! What do you suggest ?

Thank You
 

feanor

Well-Known Member
Aug 13, 2001
835
0
316
Bind is running on the machine.... right?
You can see &named& running?

What is in /var/log/messages , as far as being related to the domain you are having problems looking up?
 

sina

Active Member
Mar 7, 2002
38
0
306
And everything is fine on that machine and bind and named are both running properly. The only issue is that one domain.


dns_master_load: /var/named/*****.com.db:105: unknown RR type 'I'


dns_zone_load: zone *****.com/IN: loading master file /var/named/*****.com.db: unknown class/type

Thank You
 

feanor

Well-Known Member
Aug 13, 2001
835
0
316
Hi...........

OK it would probably take a lot longer trying to piece together what exactly is wrong with the configuration of that zone file. Why not create it over again from scratch?
Remove the zone from /var/named/DOMAIN.com.db
Remove the config lines from /etc/named.conf
(be careful)

And then use /scripts/adddns (or WHManager) to put the zone back, and finally restart the nameserver.