Submitted by kappler0 on Mon, 11/19/2012 - 23:20 Pro Licensee
Hi there, well, upon restoring a virtual server from my old system i am getting host errors which cannot seem to figure out. I believe its the hosts file from memory but i cannot remember the details... Would appreciate a pointer in the right direction here - this is from the logs:
Nov 19 23:50:16 main named: /var/named/scottkappler.com.hosts:33: localhost.*.scottkappler.com: bad owner name (check-names) Nov 19 23:50:16 main named: /var/named/scottkappler.com.hosts:34: webmail.*.scottkappler.com: bad owner name (check-names) Nov 19 23:50:16 main named: /var/named/scottkappler.com.hosts:35: admin.*.scottkappler.com: bad owner name (check-names) Nov 19 23:50:16 main named: /var/named/scottkappler.com.hosts:36: mail.*.scottkappler.com: bad owner name (check-names) Nov 19 23:50:16 main named: dns_rdata_fromtext: /var/named/scottkappler.com.hosts:37: near 'mail.*.scottkappler.com.': bad name (check-names) Nov 19 23:50:16 main named: zone scottkappler.com/IN: loading from master file /var/named/scottkappler.com.hosts failed: bad owner name (check-names) Nov 19 23:50:16 main named: zone scottkappler.com/IN: not loaded due to errors. Nov 19 23:50:16 main named: _default/scottkappler.com/IN: bad owner name (check-names) Nov 19 23:53:56 main php-cgi: PHP Warning: Module 'mcrypt' already loaded in Unknown on line 0 Nov 19 23:56:17 main named: zone localhost.localdomain/IN: loaded serial 0 Nov 19 23:56:17 main named: zone localhost/IN: loaded serial 0 Nov 19 23:56:17 main named: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0 Nov 19 23:56:17 main named: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0 Nov 19 23:56:17 main named: zone 0.in-addr.arpa/IN: loaded serial 0 Nov 19 23:56:17 main named: zone fitmedwellness.com/IN: loaded serial 1352503486 Nov 19 23:56:17 main named: zone nutritionwrx.com/IN: loaded serial 1352503509 Nov 19 23:56:17 main named: zone diabeteshealthsolution.com/IN: loaded serial 1352503533
and here is the hosts file:
$ttl 3600 @ IN SOA ns1.dealbent.net. root.ns1.dealbent.net. ( 1353386990 10800 3600 604800 38400 ) scottkappler.com. IN A 98.142.218.110 www.scottkappler.com. IN A 98.142.218.110 ftp.scottkappler.com. IN A 98.142.218.110 m.scottkappler.com. IN A 98.142.218.110 localhost.scottkappler.com. IN A 127.0.0.1 webmail.scottkappler.com. IN A 98.142.218.110 admin.scottkappler.com. IN A 98.142.218.110 mail.scottkappler.com. IN A 98.142.218.110 scottkappler.com. IN MX 5 mail.scottkappler.com. scottkappler.com. IN TXT "v=spf1 a mx a:scottkappler.com ip4:98.142.218.110 -all" cv.scottkappler.com. IN A 98.142.218.110 www.cv.scottkappler.com. IN A 98.142.218.110 cv.scottkappler.com. IN A 98.142.218.110 www.cv.scottkappler.com. IN A 98.142.218.110 ftp.cv.scottkappler.com. IN A 98.142.218.110 m.cv.scottkappler.com. IN A 98.142.218.110 localhost.cv.scottkappler.com. IN A 127.0.0.1 webmail.cv.scottkappler.com. IN A 98.142.218.110 admin.cv.scottkappler.com. IN A 98.142.218.110 mail.cv.scottkappler.com. IN A 98.142.218.110 cv.scottkappler.com. IN MX 5 mail.cv.scottkappler.com. scottkappler.com. IN NS ns1.dealbent.net. scottkappler.com. IN NS ns2.dealbent.net. *.scottkappler.com. IN A 98.142.218.110 www.*.scottkappler.com. IN A 98.142.218.110 ftp.*.scottkappler.com. IN A 98.142.218.110 m.*.scottkappler.com. IN A 98.142.218.110 localhost.*.scottkappler.com. IN A 127.0.0.1 webmail.*.scottkappler.com. IN A 98.142.218.110 admin.*.scottkappler.com. IN A 98.142.218.110 mail.*.scottkappler.com. IN A 98.142.218.110 admin.*.scottkappler.com. IN A 98.142.218.110 mail.*.scottkappler.com. IN A 98.142.218.110 *.scottkappler.com. IN MX 5 mail.*.scottkappler.com. mail.cv.scottkappler.com. IN A 98.142.218.110 cv.scottkappler.com. IN MX 5 mail.cv.scottkappler.com.
Thanks a lot!
Status:
Active
Comments
Submitted by andreychek on Mon, 11/19/2012 - 23:31 Comment #1
You may want to comment out or remove lines 33 - 37 -- I don't believe you can have a domain name that contains a wildcard in the middle, such as:
foo.*.example.com
I think it's objecting to the domains it's seeing in there with that format... the wildcard would need to be on the left of the domain name.
Submitted by kappler0 on Mon, 11/19/2012 - 23:50 Pro Licensee Comment #2
hmmm... interesting - i saw that as well.. that happened during the restore from the other server so i figured there was a purpose....
fyi: the primary server had two sub-servers cv.scottkappler.com and *.scottkappler.com (the wildcard was for a WordPress network site) - (i cannot remember how it was specifically set up now)
Submitted by kappler0 on Tue, 11/20/2012 - 00:20 Pro Licensee Comment #3
Well that fixed that issue but i ran a est with intodns.com and it tells me that my nameservers are not responding - i will however open a new ticket to keep it separate. thanks
Submitted by andreychek on Tue, 11/20/2012 - 08:04 Comment #4
Okay, I'm glad BIND starts now! I'll pass this along to Jamie, as it sounds like there may be a bug involved when restoring a Virtual Server containing a wildcard domain.
Submitted by kappler0 on Tue, 11/20/2012 - 12:06 Pro Licensee Comment #5
Hey,
There actually may be another issue i just discovered... -or- I misunderstood the restore process. The subserver cv.scottkappler.com did not restore with the main. it seemed to as it is listed as a server in the menu but the folder doesn't exist...
Do i need to restore the subserver seperately as well? It seems odd that it only restored part of the deal or am i misunderstanding how it should function? (It is a wordpress network subdomain) - and it states in vMin:
Thank you
Submitted by andreychek on Sat, 11/24/2012 - 22:20 Comment #6
I unfortunately don't know recall how Sub-Domains are handled as part of the backup process (Sub-Domain usage has been deprecated, so we don't run into it much anymore).
However, is there a separate .tar.gz file for that sub-domain in your backup directory?
If so, you'd need to make sure you restored that .tar.gz file.
However, if there isn't a separate file, that makes it sound like it may be (or should be) included as part of the parent Virtual Server's backup.