Everything should be ok. I changed the nameserver info a couple a days ago. My main site stayed on the old server and worked ok. But now when the site is on both servers it wont work on any server. I tried to add a new site to cpanel server and it worked

Whats wrong if my sites can´t be seen by name (ex. www.domain.com) but works fine if you go by ip (ex http://xxx.xxx.xxx.xx).

[/quote:0ef9494ded]
After making sure about these settings:
/etc/hosts
/etc/resolv.conf
DNS records

And if you have passed domain propagation period
And if when you use this command in ssh:

dig @127.0.0.1 server.domain.com
And you will see you dns records

But anyone outside of your server can not access to your nameservers :
You can check it by:
dig @your-nameserver-ip server.domain.com
or
http://www.dnsreport.com

The major possible issue is an incorrect firewall setting and usually this is an issue about IPchains because during server installation in red hat you selected firewall without going in details of its settings

Just stop IPchains by using this command in a root ssh session:
/etc/rc.d/init.d/ipchains stop

Then try to access your nameservers from out side of your server as I explained above, it should work
If it works then you know what is the problem your firewall settings (ipchains in this sample) .

[b:1e14d313f5]4-1) add ns1 and ns2 to your Zone database[/b:1e14d313f5]
in WHM -&amp; DNS Functions -&amp; Edit a DNS Zone
Depends on your policies you have a domain.com there, either by adding an account for domain.com or manually adding a DNS zone

Add these records in your domain.com zone database:
(Replace 10.20.30.41 and 10.20.30.42 with your nameserver IPs)
ns1 14400 IN A 10.20.30.41
ns2 14400 IN A 10.20.30.42

[b:1e14d313f5]4-2) setup ns1 and ns2 within your Domain Registrar Database[/b:1e14d313f5]
You should have ns1.domain.com and ns2.domain.com configured correctly within your Registrar database also you need to pass propagation period (approximately 5 days) then your domain is accessible by anyone on the Internet.

[b:1e14d313f5]6) Trouble shooting:[/b:1e14d313f5]
[b:1e14d313f5]Q. My DNS works on my server but does not from outside?[/b:1e14d313f5]
Make sure you have passed the propagation period and followed above instructions.
If
[b:1e14d313f5]root@host #[/b:1e14d313f5] dig @127.0.0.1 host.domain.com
works on your server but when your try from outside of your server and you will get connection timed out or name servers are unreachable:

The major possible issue is an incorrect firewall setting check your firewall you can stop it and check if your nameservers are accessible from outside of your server.

Usually this is an issue about IPchains because during server installation in Red Hat you selected firewall without going in details of its settings

Just stop IPchains by using this command in a root SSH session:
[b:1e14d313f5]root@host #[/b:1e14d313f5] /etc/rc.d/init.d/ipchains stop

Then try to access your nameservers from outside of your server as I explained above, it should work
If it works then you know what is the problem; your firewall settings (ipchains in this example)

Also please pay attention to this section in your /etc/named.conf if you haven't you can add this to your /etc/named.conf:
[quote:1e14d313f5]
options {
directory &amp;/var/named&amp;;
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
[/quote:1e14d313f5]
[b:1e14d313f5]Q. I got ndc errors?[/b:1e14d313f5]

[b:d6a9db224b]4-1) add ns1 and ns2 to your Zone database[/b:d6a9db224b]
in WHM -&amp; DNS Functions -&amp; Edit a DNS Zone
Depends on your policies you have a domain.com there, either by adding an account for domain.com or manually adding a DNS zone

Add these records in your domain.com zone database:
(Replace 10.20.30.41 and 10.20.30.42 with your nameserver IPs)
ns1 14400 IN A 10.20.30.41
ns2 14400 IN A 10.20.30.42

[b:d6a9db224b]4-2) setup ns1 and ns2 within your Domain Registrar Database[/b:d6a9db224b]
You should have ns1.domain.com and ns2.domain.com configured correctly within your Registrar database also you need to pass propagation period (approximately 5 days) then your domain is accessible by anyone on the Internet.

[b:d6a9db224b]6) Trouble shooting:[/b:d6a9db224b]
[b:d6a9db224b]Q. My DNS works on my server but does not from outside?[/b:d6a9db224b]
Make sure you have passed the propagation period and followed above instructions.
If
[b:d6a9db224b]root@host #[/b:d6a9db224b] dig @127.0.0.1 host.domain.com
works on your server but when your try from outside of your server and you will get connection timed out or name servers are unreachable:

The major possible issue is an incorrect firewall setting check your firewall you can stop it and check if your nameservers are accessible from outside of your server.

Usually this is an issue about IPchains because during server installation in Red Hat you selected firewall without going in details of its settings

Just stop IPchains by using this command in a root SSH session:
[b:d6a9db224b]root@host #[/b:d6a9db224b] /etc/rc.d/init.d/ipchains stop

Then try to access your nameservers from outside of your server as I explained above, it should work
If it works then you know what is the problem; your firewall settings (ipchains in this example)

Also please pay attention to this section in your /etc/named.conf if you haven't you can add this to your /etc/named.conf:
[quote:d6a9db224b]
options {
directory &amp;/var/named&amp;;
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
[/quote:d6a9db224b]
[b:d6a9db224b]Q. I got ndc errors?[/b:d6a9db224b]

Well i dont really understand why cPanel setups up MX records with nameservers. This is wrong. If you create an (A) record for your nameservers and your hostname an MX record is also created for each. Now i dont know about you guys but i dont send email from my nameservers.

Whats wrong if my sites can´t be seen by name (ex. www.domain.com) but works fine if you go by ip (ex http://xxx.xxx.xxx.xx).

[/quote:b0009c669d]
After making sure about these settings:
/etc/hosts
/etc/resolv.conf
DNS records

And if you have passed domain propagation period
And if when you use this command in ssh:

dig @127.0.0.1 server.domain.com
And you will see you dns records

But anyone outside of your server can not access to your nameservers :
You can check it by:
dig @your-nameserver-ip server.domain.com
or
http://www.dnsreport.com

The major possible issue is an incorrect firewall setting and usually this is an issue about IPchains because during server installation in red hat you selected firewall without going in details of its settings

Just stop IPchains by using this command in a root ssh session:
/etc/rc.d/init.d/ipchains stop

Then try to access your nameservers from out side of your server as I explained above, it should work
If it works then you know what is the problem your firewall settings (ipchains in this sample) .[/quote:b0009c669d]

1) When you say server.domain.com do you mean thunder.ourssl.com or ourssl.com?
2) Should you only have IPchains off if you are having problems with a firewall?

I am having the same problem, but only on ONE of my domain.
For that domain, 'www' doesn't work, but it works without it.
The domain has been set up for over a week now. When I ping or lookup www.domain.com, the nameserver fails.... I tried turning off the firewall, but no help.
Is this a CPanel bug?

I am having the same problem, but only on ONE of my domain.
For that domain, 'www' doesn't work, but it works without it.
The domain has been set up for over a week now. When I ping or lookup www.domain.com, the nameserver fails.... I tried turning off the firewall, but no help.
Is this a CPanel bug?

Whats wrong if my sites can´t be seen by name (ex. www.domain.com) but works fine if you go by ip (ex http://xxx.xxx.xxx.xx).

[/quote:8c00cee770]
After making sure about these settings:
/etc/hosts
/etc/resolv.conf
DNS records

And if you have passed domain propagation period
And if when you use this command in ssh:

dig @127.0.0.1 server.domain.com
And you will see you dns records

But anyone outside of your server can not access to your nameservers :
You can check it by:
dig @your-nameserver-ip server.domain.com
or
http://www.dnsreport.com

The major possible issue is an incorrect firewall setting and usually this is an issue about IPchains because during server installation in red hat you selected firewall without going in details of its settings

Just stop IPchains by using this command in a root ssh session:
/etc/rc.d/init.d/ipchains stop

Then try to access your nameservers from out side of your server as I explained above, it should work
If it works then you know what is the problem your firewall settings (ipchains in this sample) .[/quote:8c00cee770]

1) When you say server.domain.com do you mean thunder.ourssl.com or ourssl.com?
[/quote:8c00cee770]

[b:8c00cee770]ITF[/b:8c00cee770]&amp; it means thunder.ourssl.com

[quote:8c00cee770][i:8c00cee770]Originally posted by ThunderHostingDotCom[/i:8c00cee770]
2) Should you only have IPchains off if you are having problems with a firewall?[/quote:8c00cee770]
[b:8c00cee770]ITF[/b:8c00cee770]&amp; that is an example read the how-to again

domain ourssl.com
search ourssl.com
nameserver 127.0.0.1
nameserver 209.51.135.123
nameserver 209.51.135.124[/quote:25a8945bcd]
You have not to add your own local primary and secondary DNS IPs , which you have currently on your box to /etc/resolv.conf only one 127.0.0.1 is enough

only three nameserver directives are used and two of them should be nameservers which are not hosted on your current box (outsource nameservers) i.e. upstream providers' nameservers
note: only the first three nameserver ips are considered and used.

Well i dont really understand why cPanel setups up MX records with nameservers. This is wrong. If you create an (A) record for your nameservers and your hostname an MX record is also created for each. Now i dont know about you guys but i dont send email from my nameservers. [/quote:a8cfd330a1]That is something I wasn't aware of. In doing a DIG for my domain it showed: