LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 11-27-2013, 08:51 AM   #1
bradjtrammell
LQ Newbie
 
Registered: Nov 2013
Posts: 6

Rep: Reputation: Disabled
Centos 5.9 Webserver no longer resolving domain names, only IP addresses


I have a Centos 5.9 webserver that I use for personal websites, and it's been working great for about 2 months now, maybe more. All of a sudden today I attempted to access a website on the server (apsgamers.com), and there was nothing there. Normally it would display the default CentOS apache page, but there is nothing.

When I typed in the direct IP address, the default apache page (which was suppose to load) did. So I am perplexed as to why this has happened. I had this happen a year or so ago as a result of a bum update. But I have not updated this server, or installed any new software on it.

When running a check to see what services are running. I see that mysqld, httpd, named, and proftpd are all running, in fact I can ftp into the server no problem, it's simply that the websites are not resolving and not loading. When I did a check using IntoDNS.com, it reported the following errors:
Code:
SOA record
No valid SOA record came back!

MX Records
Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!

WWW A Record
ERROR: I could not get any A records for apsgamers.com!
Among several other errors related to the server's DNS not functioning (nameservers).

Anyone have any ideas how I can rescue this server?
 
Old 11-27-2013, 10:15 AM   #2
sag47
Senior Member
 
Registered: Sep 2009
Location: Raleigh, NC
Distribution: Ubuntu, PopOS, Raspbian
Posts: 1,899
Blog Entries: 36

Rep: Reputation: 477Reputation: 477Reputation: 477Reputation: 477Reputation: 477
Code:
$ dig apsgamers.com

; <<>> DiG 9.8.1-P1 <<>> apsgamers.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 6661
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;apsgamers.com.                 IN      A

;; Query time: 3421 msec
;; SERVER: REDACTED
;; WHEN: Wed Nov 27 11:12:09 2013
;; MSG SIZE  rcvd: 31
The services on the server is unlikely the problem. How do you manage your DNS on your domain? The record doesn't point to any IP address. Do you use hosted DNS? You need to talk to your domain provider as to why the domain name is not properly pointing to your authoritative DNS server.
 
Old 11-27-2013, 10:17 AM   #3
bradjtrammell
LQ Newbie
 
Registered: Nov 2013
Posts: 6

Original Poster
Rep: Reputation: Disabled
The DNS for that server is actually hosted on it. It's authoritative server hasn't changed either and does have the records pointing it to that server.

I use Webmin to manage Named and other services.
 
Old 11-27-2013, 10:23 AM   #4
sag47
Senior Member
 
Registered: Sep 2009
Location: Raleigh, NC
Distribution: Ubuntu, PopOS, Raspbian
Posts: 1,899
Blog Entries: 36

Rep: Reputation: 477Reputation: 477Reputation: 477Reputation: 477Reputation: 477
You should still talk to your domain provider (i.e. the person you bought apsgamers.com from). If you notice from my DNS dig that the record isn't pointing to any authoritative DNS servers. This is something you need to contact the support of your domain dealer about. Your sites won't work as long as the domain isn't associated with an authoritative DNS server. It doesn't matter what webmin says. The DNS dig does not lie.

As an example take the dig for google.com.

Code:
$ dig google.com
                                                                                                                                     
; <<>> DiG 9.8.1-P1 <<>> google.com                                                                                                  
;; global options: +cmd                                                                                                              
;; Got answer:                                                                                                                       
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7541                                                                             
;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 4, ADDITIONAL: 4                                                                
                                                                                                                                     
;; QUESTION SECTION:                                                                                                                 
;google.com.                    IN      A                                                                                            
                                                                                                                                     
;; ANSWER SECTION:                                                                                                                   
google.com.             92      IN      A       74.125.228.6                                                                         
google.com.             92      IN      A       74.125.228.7                                                                         
google.com.             92      IN      A       74.125.228.8                                                                         
google.com.             92      IN      A       74.125.228.9                                                                         
google.com.             92      IN      A       74.125.228.14                                                                        
google.com.             92      IN      A       74.125.228.0                                                                         
google.com.             92      IN      A       74.125.228.1                                                                         
google.com.             92      IN      A       74.125.228.2                                                                         
google.com.             92      IN      A       74.125.228.3                                                                         
google.com.             92      IN      A       74.125.228.4                                                                         
google.com.             92      IN      A       74.125.228.5                                                                         
                                                                                                                                     
;; AUTHORITY SECTION:                                                                                                                
google.com.             18978   IN      NS      ns2.google.com.                                                                      
google.com.             18978   IN      NS      ns3.google.com.                                                                      
google.com.             18978   IN      NS      ns1.google.com.                                                                      
google.com.             18978   IN      NS      ns4.google.com.                                                                      
                                                                                                                                     
;; ADDITIONAL SECTION:                                                                                                               
ns1.google.com.         195264  IN      A       216.239.32.10                                                                        
ns2.google.com.         195264  IN      A       216.239.34.10                                                                        
ns3.google.com.         195264  IN      A       216.239.36.10
ns4.google.com.         195264  IN      A       216.239.38.10

;; Query time: 0 msec
;; SERVER: REDACTED
;; WHEN: Wed Nov 27 11:25:13 2013
;; MSG SIZE  rcvd: 340
The AUTHORITY SECTION shows you the authoritative DNS servers associated with that domain name. Yours doesn't have any so queries never reach your named. Talk to your domain broker support because the problem is on their end.

Last edited by sag47; 11-27-2013 at 10:29 AM.
 
Old 11-27-2013, 10:26 AM   #5
bradjtrammell
LQ Newbie
 
Registered: Nov 2013
Posts: 6

Original Poster
Rep: Reputation: Disabled
My domain provider is GoDaddy. After checking the domain control panel. I see that my domain is pointed to the correct name servers (on another machine) which is an authoritative server. That's why I don't understand. It was working for months and months on end. This literally happened over night.
 
Old 11-27-2013, 10:34 AM   #6
sag47
Senior Member
 
Registered: Sep 2009
Location: Raleigh, NC
Distribution: Ubuntu, PopOS, Raspbian
Posts: 1,899
Blog Entries: 36

Rep: Reputation: 477Reputation: 477Reputation: 477Reputation: 477Reputation: 477
Quote:
Originally Posted by bradjtrammell View Post
My domain provider is GoDaddy. After checking the domain control panel. I see that my domain is pointed to the correct name servers (on another machine) which is an authoritative server. That's why I don't understand. It was working for months and months on end. This literally happened over night.
I'll reiterate: contact godaddy support. The problem is on their end, not yours. I don't care what web interface you look at that tells you what DNS it claims to be pointing for authoritative resolving.... the dig does not lie. Your domain is not pointing to an authoritative DNS.

EDIT:
In any case, what do your named logs say? After some googling around SERVFAIL appears when the DNS server isn't configured correctly which sounds to me like it would be the upstream vendor. What is the IP address of your server so I can further troubleshoot it's DNS from the outside?

EDIT EDIT:
A whois lookup on your domain still makes me think it is a problem on Godaddy's end.

whois apsgames.com
Quote:
Domain Name: APSGAMES.COM
Registrar URL: http://www.godaddy.com
Registrant Name: Nathan Tompkins
Registrant Organization: Allied
Name Server: NS63.DOMAINCONTROL.COM
Name Server: NS64.DOMAINCONTROL.COM
DNSSEC: unsigned

Last edited by sag47; 11-27-2013 at 10:44 AM.
 
Old 11-27-2013, 10:35 AM   #7
bradjtrammell
LQ Newbie
 
Registered: Nov 2013
Posts: 6

Original Poster
Rep: Reputation: Disabled
So even if I control the server the name servers are hosted on, the problem is still with go daddy, and not the server, or the parent server?
 
Old 11-27-2013, 10:51 AM   #8
sag47
Senior Member
 
Registered: Sep 2009
Location: Raleigh, NC
Distribution: Ubuntu, PopOS, Raspbian
Posts: 1,899
Blog Entries: 36

Rep: Reputation: 477Reputation: 477Reputation: 477Reputation: 477Reputation: 477
com points to the DNS server for apsgames.com. There is always a hierarchy so unless it is a root server your service will always depend on an upstream vendor somewhere. Here's the full record from the cli whois tool. GoDaddy just updates records to the root server for your domain information. That's why they're a registrar and not a root provider.

Code:
Domain Name: APSGAMERS.COM
Registry Domain ID: 1825894939_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Update Date: 2013-09-05 18:31:26
Creation Date: 2013-09-05 18:31:26
Registrar Registration Expiration Date: 2014-09-05 18:31:26
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.480-624-2505
Domain Status: clientTransferProhibited
Domain Status: clientUpdateProhibited
Domain Status: clientRenewProhibited
Domain Status: clientDeleteProhibited
Registry Registrant ID: 
Registrant Name: Brad Trammell
Registrant Organization: Punk Media, Inc.
Registrant Street: 8815 Brewerton Road
Registrant Street: Suite B
Registrant City: Brewerton
Registrant State/Province: New York
Registrant Postal Code: 13029
Registrant Country: United States
Registrant Phone: +1.3153134678
Registrant Phone Ext: 
Registrant Fax: +1.3155058955
Registrant Fax Ext: 
Registrant Email: domains@punkmedia.net
Registry Admin ID: 
Admin Name: Brad Trammell
Admin Organization: 
Admin Street: 8815 Brewerton Road
Admin City: Brewerton
Admin State/Province: New York
Admin Postal Code: 13029
Admin Country: United States
Admin Phone: 3155058955
Admin Phone Ext: 
Admin Fax: 
Admin Fax Ext: 
Admin Email: brad.j.trammell@gmail.com
Registry Tech ID: 
Tech Name: Brad Trammell
Tech Organization: 
Tech Street: 8815 Brewerton Road
Tech City: Brewerton
Tech State/Province: New York
Tech Postal Code: 13029
Tech Country: United States
Tech Phone: 3155058955
Tech Phone Ext: 
Tech Fax: 
Tech Fax Ext: 
Tech Email: brad.j.trammell@gmail.com
Name Server: CS5.PUNKMEDIA.CO
Name Server: CS6.PUNKMEDIA.CO
DNSSEC: unsigned
Is it correct to assume your name server is CS5.PUNKMEDIA.CO and CS6.PUNKMEDIA.CO?

Last edited by sag47; 11-27-2013 at 10:52 AM.
 
Old 11-27-2013, 10:54 AM   #9
bradjtrammell
LQ Newbie
 
Registered: Nov 2013
Posts: 6

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by sag47 View Post
Is it correct to assume your name server is CS5.PUNKMEDIA.CO and CS6.PUNKMEDIA.CO?
Yes, that is the correct name server. And has not been changed since the domain was purchased. That's why I can't understand why it would be on godaddy's end because everything is hosted by me, all they host is the actual domain. Everything else should point directly to my servers.
 
Old 11-27-2013, 10:58 AM   #10
bradjtrammell
LQ Newbie
 
Registered: Nov 2013
Posts: 6

Original Poster
Rep: Reputation: Disabled
I just noticed you misspelled the who is domain check. It's actually APSGAMERS.com, not APSGAMES. That's why it's showing as Godaddy's name servers. This is the correct who is records:

Quote:
Domain Name: APSGAMERS.COM
Registrar URL: http://www.godaddy.com
Registrant Name: Brad Trammell
Registrant Organization: Punk Media, Inc.
Name Server: CS5.PUNKMEDIA.CO
Name Server: CS6.PUNKMEDIA.CO
DNSSEC: unsigned
I also just noticed that this is not the only affected domain, it seems all the domains are doing this. There are about 10 domains on this server, and none of them are resolving either. They're all pointed to the same place (cs5.punkmedia.co & cs6.punkmedia.co)

Last edited by bradjtrammell; 11-27-2013 at 11:00 AM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Webalizer not resolving IP addresses into host names in Ubuntu 12.04 LTS dibya Linux - Newbie 2 09-11-2013 07:26 AM
Strange Issues Resolving Domain Names klarsen Linux - Networking 2 10-29-2009 09:50 AM
slow resolving of domain names DarkAge Linux - Networking 10 05-29-2009 05:23 PM
Issues Resolving Domain Names whc Linux - Server 6 03-13-2008 04:28 PM
Mandrake 9.1 not resolving domain names erikbennett Mandriva 2 10-06-2003 04:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 09:13 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration