DNS went poof?

rndinit0

Verified User
Joined
Jan 15, 2005
Messages
91
[solved] Broken DNS post Admin/Backup - Transfer

I recently moved all my clients from one box to another. (oldbox & newbox resp.)

I updated ns1.oldbox.com ns2.oldbox.com to use the same ips as:

ns1.newbox.com
ns2.newbox.com

But now *.oldbox.com wont resolve for some odd reason. The registrar nameserver IP change was done on the 22nd of april.

Any ideas why this is happening?


oldbox = ns1.liquidmemory.net
newbox = ns1.tribe9.com
 
Last edited:
Ok here is what I've done so far:

1.) Admin Backup Transfer from condor.liquidmemory.net to alpha.tribe9.com
2.) Logged into enom (registrar) updated ns1.liquidmemory.net & ns2.liquidmemory.net to 64.125.185.58 & 59 (respectively)
3.) Changed ns1.liquidmemory.net ns2.liquidmemory.net A record on alpha.tribe9.com to 64.126.185.58 & .59

Problem:

Domains: liquidmemory.net vectorisme.com fail to resolve (there could be more domains but Im not sure at this point)

Im missing something here, and cant seem to make any progress.

Here is the output from my registrar when I check on the status of the nameservers: liquidmemory.net

PHP:
attrib-id: 	56576943_HOST_CNE-VRSN
ipaddress: 	64.125.185.58
attrib-upid: 	enom
name: 	ns1.liquidmemory.net
attrib-crid: 	cosmos
status: 	ok
linked
attrib-update: 	2008-04-22T11:22:10.0000Z
attrib-crdate: 	2005-08-05T21:01:37.0000Z
attrib-clid: 	048

attrib-id: 	56576944_HOST_CNE-VRSN
ipaddress: 	64.125.185.59
attrib-upid: 	enom
name: 	ns2.liquidmemory.net
attrib-crid: 	cosmos
status: 	ok
linked
attrib-update: 	2008-04-22T11:22:46.0000Z
attrib-crdate: 	2005-08-05T21:01:49.0000Z
attrib-clid: 	048

------------------------------
nameservers: tribe9.com

attrib-id: 	62143750_HOST_CNE-VRSN
ipaddress: 	64.125.185.58
attrib-upid: 	enom
name: 	ns1.tribe9.com
attrib-crid: 	enom
status: 	ok
linked
attrib-update: 	2008-04-19T21:34:12.0000Z
attrib-crdate: 	2008-04-19T21:34:12.0000Z
attrib-clid: 	048

attrib-id: 	62143753_HOST_CNE-VRSN
ipaddress: 	64.125.185.59
attrib-upid: 	enom
name: 	ns2.tribe9.com
attrib-crid: 	enom
status: 	ok
linked
attrib-update: 	2008-04-19T21:34:36.0000Z
attrib-crdate: 	2008-04-19T21:34:36.0000Z
attrib-clid: 	048

liquidmemory.net zone file
PHP:
ftp	A	64.125.185.60	
liquidmemory.net.	A	64.125.185.60	
localhost	A	127.0.0.1	
mail	A	64.125.185.60	
ns1.liquidmemory.net.	A	64.125.185.58	
ns2.liquidmemory.net.	A	64.125.185.59	
pay	A	64.125.185.60	
pop	A	64.125.185.60	
www	A	64.125.185.60	
www.pay	A	64.125.185.60	
liquidmemory.net.	NS	ns1.liquidmemory.net.	
liquidmemory.net.	NS	ns2.liquidmemory.net.	
ALT1.ASPMX.L.GOOGLE.COM.	MX	10	
ALT2.ASPMX.L.GOOGLE.COM.	MX	10	
ASPMX.L.GOOGLE.COM.	MX	0	
ASPMX2.GOOGLEMAIL.COM.	MX	20	
ASPMX3.GOOGLEMAIL.COM.	MX	20	
ASPMX4.GOOGLEMAIL.COM.	MX	20	
ASPMX5.GOOGLEMAIL.COM.	MX	20	
google80c3b56c67990d32.liquidmemory.net.	CNAME	google.com.	
mail	CNAME	ghs.google.com.	
60.185.125.64.in-addr.arpa	PTR	mail.liquidmemory.net.	
liquidmemory.net.	TXT	"v=spf1 a mx ip4:64.125.185.60 ?all"

tribe9.com zone file
PHP:
ftp	A	64.125.185.57	
localhost	A	127.0.0.1	
mail	A	64.125.185.57	
ns1.tribe9.com.	A	64.125.185.58	
ns2.tribe9.com.	A	64.125.185.59	
pop	A	64.125.185.57	
tribe9.com.	A	64.125.185.57	
www	A	64.125.185.57	
tribe9.com.	NS	ns1.tribe9.com.	
tribe9.com.	NS	ns2.tribe9.com.	
mail	MX	10	
tribe9.com.	TXT	"v=spf1 a mx ip4:64.125.185.57 ?all"
 
Last edited:
/var/log/messages output
PHP:
Apr 25 19:12:15 alpha named[18699]: shutting down
Apr 25 19:12:15 alpha named[18699]: stopping command channel on 127.0.0.1#953
Apr 25 19:12:15 alpha named[18699]: no longer listening on 127.0.0.1#53
Apr 25 19:12:15 alpha named[18699]: no longer listening on 64.125.185.57#53
Apr 25 19:12:15 alpha named[18699]: no longer listening on 208.185.81.9#53
Apr 25 19:12:15 alpha named[18699]: no longer listening on 64.125.185.58#53
Apr 25 19:12:15 alpha named[18699]: no longer listening on 64.125.185.59#53
Apr 25 19:12:15 alpha named[18699]: no longer listening on 64.125.185.60#53
Apr 25 19:12:15 alpha named[18699]: no longer listening on 64.125.185.61#53
Apr 25 19:12:15 alpha named[18699]: exiting
Apr 25 19:12:15 alpha named[18809]: starting BIND 9.3.3rc2 -u named
Apr 25 19:12:15 alpha named[18809]: found 1 CPU, using 1 worker thread
Apr 25 19:12:15 alpha named[18809]: loading configuration from '/etc/named.conf'
Apr 25 19:12:15 alpha named[18809]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 25 19:12:15 alpha named[18809]: listening on IPv4 interface eth0, 64.125.185.57#53
Apr 25 19:12:15 alpha named[18809]: listening on IPv4 interface eth0:10, 208.185.81.9#53
Apr 25 19:12:15 alpha named[18809]: listening on IPv4 interface eth0:0, 64.125.185.58#53
Apr 25 19:12:15 alpha named[18809]: listening on IPv4 interface eth0:1, 64.125.185.59#53
Apr 25 19:12:15 alpha named[18809]: listening on IPv4 interface eth0:2, 64.125.185.60#53
Apr 25 19:12:15 alpha named[18809]: listening on IPv4 interface eth0:3, 64.125.185.61#53
Apr 25 19:12:15 alpha named[18809]: command channel listening on 127.0.0.1#953
Apr 25 19:12:15 alpha named[18809]: zone 0.0.127.in-addr.arpa/IN: loading master file named.local: file not found
Apr 25 19:12:15 alpha named[18809]: zone albarraak.com/IN: loaded serial 2008042101
Apr 25 19:12:15 alpha named[18809]: zone aliaknoiak.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: dns_master_load: /var/named/alraeeseco.com.db:36: mail.alraeeseco.com: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone alraeeseco.com/IN: loading master file /var/named/alraeeseco.com.db: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone alrouyah.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone ananyah.com/IN: loaded serial 2008042101
Apr 25 19:12:15 alpha named[18809]: zone arinshant.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone bader-art.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone bedirian.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone bokandar.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone buaijan.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone bubyancorp.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone bukandar.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone cggts.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone chicintuition.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: dns_master_load: /var/named/concept5point3.com.db:35: mail.concept5point3.com: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone concept5point3.com/IN: loading master file /var/named/concept5point3.com.db: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone design-idg.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone einstein9.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone er-ad.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone esh6a.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone eve-tygris.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: dns_master_load: /var/named/expgas.com.db:38: mail.expgas.com: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone expgas.com/IN: loading master file /var/named/expgas.com.db: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone fawaresholding.com/IN: loaded serial 2008042101
Apr 25 19:12:15 alpha named[18809]: zone kandary.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone kanderi.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone kandery.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone lewisnlambertofs.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone mahyawa.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: dns_master_load: /var/named/mmotribe.com.db:40: mail.mmotribe.com: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone mmotribe.com/IN: loading master file /var/named/mmotribe.com.db: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone noaimi.com/IN: loaded serial 2008042101
Apr 25 19:12:15 alpha named[18809]: zone noura-moda.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone q8cartoons.com/IN: loaded serial 2008042202
Apr 25 19:12:15 alpha named[18809]: zone q8lawyers.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: dns_master_load: /var/named/shanfa.com.db:38: mail.shanfa.com: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone shanfa.com/IN: loading master file /var/named/shanfa.com.db: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone silentrunners.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone sou-varne.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone spgroup-kw.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone tribe9.com/IN: loaded serial 2008042001
Apr 25 19:12:15 alpha named[18809]: zone alpha.tribe9.com/IN: loaded serial 2008041600
Apr 25 19:12:15 alpha named[18809]: zone tristarkw.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone trueblue-translation.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone unixgtc.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: dns_master_load: /var/named/upc-kwt.com.db:35: mail.upc-kwt.com: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone upc-kwt.com/IN: loading master file /var/named/upc-kwt.com.db: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone usbhak.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: dns_master_load: /var/named/vectorisme.com.db:35: mail.vectorisme.com: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone vectorisme.com/IN: loading master file /var/named/vectorisme.com.db: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone whitehorse-kwt.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone xploitbox.com/IN: loaded serial 2008042201
Apr 25 19:12:15 alpha named[18809]: zone yourrealcards.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone yuyee22.com/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone zokume.com/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone xploitbox.info/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone localhost/IN: loading master file localhost.zone: file not found
Apr 25 19:12:15 alpha named[18809]: zone agool.net/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone alalsun.net/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone bedirian.net/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone crazydevil.net/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone decorum-inc.net/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone einstein9.net/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone iat-rak.net/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone knights-sg.net/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: dns_master_load: /var/named/liquidmemory.net.db:32: mail.liquidmemory.net: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone liquidmemory.net/IN: loading master file /var/named/liquidmemory.net.db: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone noaimi.net/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone q8cartoon.net/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone q8cartoons.net/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone smsthem.net/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone tdih.net/IN: loaded serial 2008042102
Apr 25 19:12:15 alpha named[18809]: zone tribalsage.net/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone usbhak.net/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: dns_master_load: /var/named/uutc.net.db:35: mail.uutc.net: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone uutc.net/IN: loading master file /var/named/uutc.net.db: CNAME and other data
Apr 25 19:12:15 alpha named[18809]: zone vpnx.net/IN: loaded serial 2008042201
Apr 25 19:12:15 alpha named[18809]: zone xploitbox.net/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone yourrealcards.net/IN: loaded serial 2008042200
Apr 25 19:12:15 alpha named[18809]: zone agool.org/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone da-wiki.org/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: zone tribalsage.org/IN: loaded serial 2008042101
Apr 25 19:12:15 alpha named[18809]: zone obslimited.us/IN: loaded serial 2008042100
Apr 25 19:12:15 alpha named[18809]: running
Apr 25 19:12:15 alpha named[18809]: zone alpha.tribe9.com/IN: sending notifies (serial 2008041600)
Apr 25 19:12:15 alpha named[18809]: zone trueblue-translation.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone tribe9.com/IN: sending notifies (serial 2008042001)
Apr 25 19:12:15 alpha named[18809]: zone cggts.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone agool.net/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone alalsun.net/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone da-wiki.org/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone aliaknoiak.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone tribalsage.net/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone agool.org/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone tribalsage.org/IN: sending notifies (serial 2008042101)
Apr 25 19:12:15 alpha named[18809]: zone zokume.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone esh6a.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone whitehorse-kwt.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone albarraak.com/IN: sending notifies (serial 2008042101)
Apr 25 19:12:15 alpha named[18809]: zone xploitbox.com/IN: sending notifies (serial 2008042201)
Apr 25 19:12:15 alpha named[18809]: zone chicintuition.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone noaimi.com/IN: sending notifies (serial 2008042101)
Apr 25 19:12:15 alpha named[18809]: zone alrouyah.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone design-idg.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone ananyah.com/IN: sending notifies (serial 2008042101)
Apr 25 19:12:15 alpha named[18809]: zone bubyancorp.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone obslimited.us/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone bedirian.net/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone iat-rak.net/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone smsthem.net/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone sou-varne.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone buaijan.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone lewisnlambertofs.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone tristarkw.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone bokandar.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone xploitbox.net/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone noaimi.net/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone bader-art.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone fawaresholding.com/IN: sending notifies (serial 2008042101)
Apr 25 19:12:15 alpha named[18809]: zone tdih.net/IN: sending notifies (serial 2008042102)
Apr 25 19:12:15 alpha named[18809]: zone crazydevil.net/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone mahyawa.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone er-ad.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone bedirian.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone vpnx.net/IN: sending notifies (serial 2008042201)
Apr 25 19:12:15 alpha named[18809]: zone bukandar.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone decorum-inc.net/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone eve-tygris.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone q8cartoons.com/IN: sending notifies (serial 2008042202)
Apr 25 19:12:15 alpha named[18809]: zone usbhak.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone kandery.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone noura-moda.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone q8cartoon.net/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone xploitbox.info/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone knights-sg.net/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone arinshant.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone yuyee22.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone q8cartoons.net/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: client 64.125.185.59#36834: received notify for zone 'alpha.tribe9.com'
Apr 25 19:12:15 alpha named[18809]: zone kanderi.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone silentrunners.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone spgroup-kw.com/IN: sending notifies (serial 2008042100)
Apr 25 19:12:15 alpha named[18809]: zone einstein9.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone usbhak.net/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone yourrealcards.net/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone q8lawyers.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone yourrealcards.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone einstein9.net/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone kandary.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: zone unixgtc.com/IN: sending notifies (serial 2008042200)
Apr 25 19:12:15 alpha named[18809]: client 64.125.185.59#36834: received notify for zone 'tribe9.com'
Apr 25 19:13:35 alpha named[18809]: lame server resolving 'c9359430.virtua.com.br' (in 'virtua.com.br'?): 201.6.0.102#53
Apr 25 19:16:11 alpha named[18809]: unexpected RCODE (REFUSED) resolving '18.150.46.195.in-addr.arpa/PTR/IN': 213.194.65.36#53

Ive noticed all domains that have " dns_master_load: " directive do not resolve properly.
 
I figured out what the problem is:


When you do a Admin - Backup/Transfer, DirectAdmin adds an A record for mail.

PHP:
mail	A	64.125.185.60
mail	CNAME	ghs.google.com.


The above is the result for domains that use google apps to process mail.
This breaks the zone file, and hence it wont resolve, and will frustrate the administrator.

All is well that ends well.
 
We've done multiple admin backups and have never had DirectAdmin and have never noticed that. Did you by any chance set up the domain on the new server before you restored it?

Jeff
 
The dns restore is a rather complex process.
It has to merge the backed up db file with the OLD ip address into a already existant live db file, with the NEW ip. It has to also swap the old IPs around into the new values.. overwrite new values with old ones, maintain old custom values with totally different IPs.. prevent duplicates, and repeat this process for each and every record type, customized for what that type does.

In this case, when you do a restore, the empty domain is created in DA first. All defaults are added to DA. This includes the "mail" A record.

The backup likely has no "mail" A record at all.. just a CNAME, in your case.

The restore tool now has conflicting information and won't know which of the 2 types to import. The new zone is allowed to be live (this can be a live domain for some time)... For example, you can create the domain in DA, add 3 new subdomains that didn't exist on the old box... do a restore 2 weeks later from the old box with 3 different subdomains, and it has to swap old data , merge zones with the live zone, without deleting anything, giving you 6 subdomains total.

As for your case.. you'd probably want the mail A record to be deleted... but what if this new box uses a different mail setup than the old box? In that case perhaps deleting the CNAME from the old zone would be the proper procedure. It's hard for DA to predict what actions you'd want it to take.

It's all a very messy and complicated piece of code.
If I had to make any suggestions.. it would be to not use CNAMES...but instead add an "A" record resolving to the value that ghs.google.com resovles to, if at all possible (eg: 72.14.207.121).

Past that, since the issue may be beyond what DA can reasonably predict and you absolutely require the CNAMEs (which may be the case), you may just need to adjust each zone as it comes in.

John
 
The only reason why I pointed out DA's behaviour was so that others could learn from my mistakes. This was my 1st ever DA admin backup/transfer server migration.

A records to google services would not be a wise idea, since they might change their ips more frequently.

I understand that its a complex script, and it has done most of the hardwork for me. Having to only edit 6 dns zones, and deleting the extra A record is not an issue.
 
I think the easy way to resolve such conflicts would be by adding a new package field: use external mailservers - yes/no. This will provide DA with valuable information it doesn't currently have.
For accounts that use external mailservers there is probably no point to add "mail" A record. On the other hand, for accounts using local mailserver "mail" A record is reasonably expected.

Just my 2 cents...
 
It's all a very messy and complicated piece of code.
If I had to make any suggestions.. it would be to not use CNAMES...but instead add an "A" record resolving to the value that ghs.google.com resovles to, if at all possible (eg: 72.14.207.121).
When the DNS CNAME record was invented, it's purpose was to point to records in zones over which you have no control. If you have no control over a zone you really don't want an A record with an IP# which could easily become obsolete.

(The proof that CNAME was meant to point only to zones over which you have no control is that if you have a CNAME for the same zone no other records for that specific DNS service/subdomain entry will work.)

Understanding the problem, I still think it important to use CNAME records when pointing to subdomains/resources in zones over which you have no control.
Past that, since the issue may be beyond what DA can reasonably predict and you absolutely require the CNAMEs (which may be the case), you may just need to adjust each zone as it comes in.
Sounds good to me ;).

Jeff
 
For accounts that use external mailservers there is probably no point to add "mail" A record. On the other hand, for accounts using local mailserver "mail" A record is reasonably expected.
Not reasonable at all from my point of view. You may very well need an A record, but to a different IP# pointing to a different server. As John points out, DNS is complex.
I think the easy way to resolve such conflicts would be by adding a new package field
It wouldn't easily work that way; restores have to ignore packages. If they didn't they might not be able to complete for one reason or another.

Jeff
 
Actually if you log in as the user, DNS Administration > Edit MX Records > Use External Mail server. Im not sure if Admin Backup/Restore takes that into consideration when restoring. But that would be the easy way to avoid having A record & cname record conflicts if the Admin Back script could remember that setting, when backing up. And when it restores, it should obviously not add an A record.
 
It's actually backwards. If we added a conflict check, the CNAME wouldn't get added, because the defaults exist first. The restores all assume that the domain was already live beforehand. The defaults have priority because of this. As I mentioned, it's a bit complex.

John
 
Couldn't you just copy the zone from old server and use it to replace the zone on the new server and then swap the ip's? That the new zone is exactly like the old zone except for the new ip. Custom changes remain intact.
 
Not reasonable at all from my point of view. You may very well need an A record, but to a different IP# pointing to a different server. As John points out, DNS is complex.
What I meant was no point to add "mail" A record automatically.
You might need to create an A record, but the default record as it is created now won't work for you anyway.

It wouldn't easily work that way; restores have to ignore packages. If they didn't they might not be able to complete for one reason or another.
The restore procedure restores accounts with the same properties, right? I mean, things like disk quota, limits on mailboxes, FTP accounts, # of domains/domain pointers etc are all restored. It might not restore the package name, but everything else should match the original account or it wouldn't be called a backup :)
 
Ok, what I've done, is added a loop go to through all CNAME records in the backup db file. If any of them match up with the merged A record pile, then the merged A record that matches will be deleted. Avaiable for the next release. If anyone can see any reason why this may not be a good idea, let me know, but seeing how a matching CNAME and A would totally kill the entire zone anyway, 1 broken A record is better than an entirely totally non-responsive domain.

John
 
May be I wasn't clear enough in my original post.
Right now when you create an account, you can specify, for example, whether SSH is available for this account. The field that stores this data is what I called a "package field". May be I should've called it an account property.

Just imagine there is an account property that specifies whether the account uses local or external mailserver.
For local mailserver - everything remains the same.
For external mailserver - no default "mail" A record created automatically, so there is no conflict that would prevent you from restoring CNAME or custom mail A record.

I think this is a pretty straightforward logic and it will surely make restores easier for anyone using Google Mail.
 
Yes, the above changes should work for that case. The mail "A" record will be removed and the CNAME will have priority.

John
 
Back
Top