| Posted by ttgt, 03-20-2010, 01:13 AM | | Hi,
i ssh to my server and want to change particular subdomain from ip 1.1.1.1 to 2.2.2.2,
i edit my /var/named/mydomain.com.db and save and restart named,
but over days,the ip still point to 1.1.1.1,
is it possible any reason make it ?
thanx
ps.my server is centos with cpanel.
|
| Posted by jweeb, 03-20-2010, 01:17 AM | | you may want to use intodns.com to diagnose your subdomain issues.
|
| Posted by Hostwaresupport, 03-20-2010, 02:37 AM | | I am just wondering, if you are using cPanel why did you edit named.conf manually? Anyways, make sure that you have added correct 'A' entry for that subdomain and use intodns.com in order to find out exact problem..
|
| Posted by ianeeshps, 03-20-2010, 03:15 AM | | check your name server which points to the server which you done the modification, suppose if u change int in dns1.dnsserver.com
then check it bye,dns1.dnsserver.com
host subdomain @dns1.dnsserver.com whether to identify the server is resolving the ip address correctly or not.
|
| Posted by madaboutlinux, 03-20-2010, 11:54 AM | | You may have set the 'A' record of the sub-domain properly in the /var/named/mydomain.com.db file but are the name servers assigned to "mydomain.com" are resolving to your server?
If the name servers assigned to mydomain.com are hosted elsewhere, you need to change the A record of the sub-domain on those servers and not on your server.
BTW, make sure if you have chroot'ed named, if yes, you have to edit the file at /var/named/chroot/var/named/mydomain.com.db. The better way is to edit the DNS zone from the option
|
| Posted by VIPoint, 03-20-2010, 05:08 PM | | Make sure that you restart named for the changes to take place. Try restarting named service after making the changes and it should work.
|
| Posted by jadursupport, 03-20-2010, 08:50 PM | | you can check the logs if there is any problem with the zone updates and also you should check if the subdomain resolving it locally correctly using following command from shell
dig subdomain.maindomain.com @localhost
and check if its resolve to correct IP if so then its the propagation issue probably.
|
| Posted by UNIXy, 03-20-2010, 09:05 PM | | Be sure to increase the serial value by one then run rndc reload.
Regards
Joe / UNIXy
|
|
 Add to Favourites
 Print this Article
|
