ispCP - Board - Support
Domain Resolution - Printable Version

+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Development Area (/forum-1.html)
+--- Forum: General discussion (/forum-11.html)
+--- Thread: Domain Resolution (/thread-406.html)

Domain Resolution - andars - 04-19-2007 08:12 AM

admin.ravenholt.info doesn't seem to resolve. My name servers are resolving(ns1.ravenholt.info/ns2.ravenholt.info). I realize that ravenholt.info is currently resolving to an incorrect local IP. However, I'm a little confused as to how to fix everything. Should I put my local IP or WAN IP in during install?

An example domain I setup under a reseller has a bind file which looks like this:

/var/cache/bind/game-sales.info.db

Code:
$TTL 86400
@       IN      SOA     ns.game-sales.info. root.game-sales.info. (
; dmn [game-sales.info] timestamp entry BEGIN.
                        2007041800
; dmn [game-sales.info] timestamp entry END.
                        8H
                        2H
                        4W
                        1D
)
                IN      NS      ns1.game-sales.info.
                IN      NS      ns2.game-sales.info.
                IN      MX      10 mail.game-sales.info.

game-sales.info.        IN      A       192.168.1.105
game-sales.info.        IN      TXT     "v=spf1 a mx ip4:192.168.1.105 ~all"
ns1             IN      A       192.168.1.105
ns2             IN      A       192.168.1.105
mail            IN      A       192.168.1.105

I'm unfamiliar with bind but it concerns me that none of the records point to an outward IP address. However, if I setup everything using my WAN IP nothing resolves and every added domain points the ISPCP login panel.

RE: Domain Resolution - andars - 04-19-2007 03:17 PM

Edit: I guess the below really doesn't work. Now they just resolve to the new domain I entered under a reseller... sigh. I've been at this for hours.

I had to use this:

Code:
Q.my ips are resolving private to the outside (dnsreport.com report private ips instead of public ones)
There's two methods to solve this problem, i will state one now, the second one will be added later

this method consist of reinstalling VHCS with public IP, and solve apache resolving problem (when public ip is used, apache will no longer resolve domains)
first you need to remove all added users (go to vhcs2 database in mysql and see the uid in admin table)

Code:
sudo userdel vu200Xwhere X is the user number (vhcs2 will begin with 1)

remove the added groups

Code:
sudo groupdel vu200Xwhere X is the group number (vhcs2 will begin with 1)

remove the working conf files

Code:
sudo rm /etc/vhcs2/apache/working/vhcs2.conf
sudo rm /etc/vhcs2/bind/working/*
sudo rm /etc/apache2/sites-available/vhcs2.conf
sudo rm /var/cache/bind/*now you're ready to install, repeat only step 11 but use public ip this time

now proceed to edit the apache files to resolve correctly
Open /etc/vhcs2/apache/parts/{prefix}_entry.tpl where {prefix} is "als" and "dmn" and "sub" without quotes
replace

Code:
<VirtualHost {DMN_NAME}>with

Code:
<VirtualHost *>recreate reseller, etc... now

Found here: http://ubuntuforums.org/showthread.php?t=25722