URGENT: All sites offline

Richard G said:
As I said before, remove the correspondig line from your directadmin.conf.

So go to /usr/local/directadmin/conf and open directadmin.conf.
Remove this line:
ssl_redirect_host your.hostname.com
save and closed the file, restart directadmin and you're done.

First have your directadmin and named running correct, before starting fixing nameserver issues. ;)
Click to expand...

Thanks I already have access do DA. But I still have issues on DNS Zone. The service named shows as running on DA. I was thinking that was down.
But...
when I go to domain registrar to setup the ns1 and ns2 IPs for the main server account, it says timeout.
The DNS entries seems to be ok on server. But, when I go to website intodns.com and insert my domain shows at red the following records:

SOA record
MX Records
WWW A Record
DNS servers responded

any idea?
 
jdn1976 said:
Thanks I already have access do DA. But I still have issues on DNS Zone. The service named shows as running on DA. I was thinking that was down.
But...
Click to expand...
This might have something to do with ipv6 as I read this error on page 1 of this thread:
Code: 
network unreachable resolving './NS/IN': 2001:500:200::b#53
That last part looks to me as ipv6.

This make me wonder, if you're indeed using ipv6, did you setup your Directadmin for use with ipv6?

Als, it might be necessary to open port 53 for ipv6 in your /etc/named.conf file (remove the // in front of it), but I'm not sure. However, this can all have to do with the dns issues your having, but it can also be something completely different and hard to say without seeing what's going on exactly.

For this reason I fully agree with @apogee that it might be wise to get a quote from Zeiter or Smtalk, they are both very good in fixing issues and also very fast.
 
Richard G said:
This might have something to do with ipv6 as I read this error on page 1 of this thread:
Code: 
network unreachable resolving './NS/IN': 2001:500:200::b#53
That last part looks to me as ipv6.

This make me wonder, if you're indeed using ipv6, did you setup your Directadmin for use with ipv6?

Als, it might be necessary to open port 53 for ipv6 in your /etc/named.conf file (remove the // in front of it), but I'm not sure. However, this can all have to do with the dns issues your having, but it can also be something completely different and hard to say without seeing what's going on exactly.

For this reason I fully agree with @apogee that it might be wise to get a quote from Zeiter or Smtalk, they are both very good in fixing issues and also very fast.
Click to expand...

It is odd. Yesterday server was fine. Can an background updates do something.
I use ipv4
Richard G said:
This might have something to do with ipv6 as I read this error on page 1 of this thread:
Code: 
network unreachable resolving './NS/IN': 2001:500:200::b#53
That last part looks to me as ipv6.

This make me wonder, if you're indeed using ipv6, did you setup your Directadmin for use with ipv6?

Als, it might be necessary to open port 53 for ipv6 in your /etc/named.conf file (remove the // in front of it), but I'm not sure. However, this can all have to do with the dns issues your having, but it can also be something completely different and hard to say without seeing what's going on exactly.

For this reason I fully agree with @apogee that it might be wise to get a quote from Zeiter or Smtalk, they are both very good in fixing issues and also very fast.
Click to expand...

Thats odd. Yesterday the server was running fine until yesterday night.
As far I know my VPS datacenter provided ipv4 IPs. Inside /etc/resolv.conf I have:

# Generated by NetworkManager
nameserver 186.202.26.26
nameserver 186.202.27.27

When I setup the server 3 or 4 weeks ago I setup with IPv4... and never had this kind of problem.
Yes, the port 53 is open on the firewall. And /etc/named.conf I have // there. I try to remove, restart named, but do not solve, unless I need time for propagation?
 
The /etc//resolv.conf file is only for lookups, those are probably from your VPS provider.
However the error on the first page is an ipv6 error. It might be of no harm, but one never knows.

If you onlyuse ipv4 you can put the // back in your /etc/named.conf because then you don't need to remove them.

Ofcourse on your own nameservers you need time to propagate, but this mostly does not take more then 24 hours.

If you have 2 nameservers locally on 2 ip's (so your own namservers), then it might be wise to also add your own nameserver to /etc/resolv.conf like this:

# Generated by NetworkManager
nameserver 127.0.0.1
nameserver 186.202.26.26
nameserver 186.202.27.27

This will not fix any named issues, but can help with local lookups by for example exim and spamassassin.

You might also try to have Named only run on ipv4 by editting /etc/sysconfig/named and add this line like this:
Code: 
OPTIONS="-4"
restart named.

This should at least take care of ipv6 errors in the logs, so they won't show up anymore.

But if you setup the server 3 or 4 weeks ago, there can not be any propagation issue. Maybe a routing issue with your vps host or datacenter or something could also be the case maybe?
 
Richard G said:
The /etc//resolv.conf file is only for lookups, those are probably from your VPS provider.
However the error on the first page is an ipv6 error. It might be of no harm, but one never knows.

If you onlyuse ipv4 you can put the // back in your /etc/named.conf because then you don't need to remove them.

Ofcourse on your own nameservers you need time to propagate, but this mostly does not take more then 24 hours.

If you have 2 nameservers locally on 2 ip's (so your own namservers), then it might be wise to also add your own nameserver to /etc/resolv.conf like this:

# Generated by NetworkManager
nameserver 127.0.0.1
nameserver 186.202.26.26
nameserver 186.202.27.27

This will not fix any named issues, but can help with local lookups by for example exim and spamassassin.

You might also try to have Named only run on ipv4 by editting /etc/sysconfig/named and add this line like this:
Code: 
OPTIONS="-4"
restart named.

This should at least take care of ipv6 errors in the logs, so they won't show up anymore.

But if you setup the server 3 or 4 weeks ago, there can not be any propagation issue. Maybe a routing issue with your vps host or datacenter or something could also be the case maybe?
Click to expand...


Issue solved... and not solved. It is a problem on datacenter, I talk to them and they say that block port 53.
Just to add. the TCP was open, but the UDP is closed. That is why is giving error.
It is odd because it was working 2 or 3 weeks ago fine.

Anyway: it was not a DA problem and not an issue on server configuration. I just lost 2 days of my life because of this VPS on datacenter. I need to find one that allows port 53 UDP/TCP here in Brazil.

Thank you guys for your help and attention given to me.
 
Very odd they close port 53 UDP, however named should also be able to work via TCP.
I presume they did not give a reason for closing this port and were not prepared to open it?

Anyway, good to hear we found the cause of the issue, at least you can do something about it now. However, it's no fun to have to move your VPS for such odd reason cause by the datacenter.
 
You must log in or register to reply here.
Back
Top