This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.

virtual domain urgent help

7 posts / 0 new

Topic locked

Last post

#1 Fri, 11/21/2008 - 06:11

jiontro

virtual domain urgent help

i'ved installed debian 4.0r4 i386 and after i'ved installed virtualmin 3.6 GPL from the script and all seems ok, no errors; i'ved created my first virtual domain, ip based, like http://jiontro.net on a virtual ip : 192.168.0.1 , all seems ok but when i try to acces it from an extern ip, it cannot be accessed, but when i type from the server this address, works. Any help pls

Ioan

#2 Fri, 11/21/2008 - 06:37

jdamron

local IP's can not be seen from the outside 192.168 is a local ip you have to have your roughter point a outside Ip to this local IP
John

#3 Thu, 04/16/2009 - 05:58 (Reply to #2)

duncanbbd

not sure if I get this right ?

if your server internal IP address is 192.168.0.1 and you have it connected to a router connected to the internet. you need to use Dynamic DNS to get a domain to point to your router and also set up your router to connect port 80 to 192.168.0.1

is 82.77.208.172 your external IP address ?

#4 Thu, 04/16/2009 - 09:02 (Reply to #3)

ronald

the solution to your problem is actually much simpler.
In order to find a domain on the internet you first have to register this domain.

jiontro.net
Server Data
Domain Status: Never Registered Before

So how about you buy this domain at let's say Namecheap.com and point it to your server first?

#5 Fri, 05/15/2009 - 19:05 (Reply to #4)

jiontro

thanks...just now i understude how it work and the ways of the internet, i thought that i can make my debi dns server.... i still have some questions!!!

#6 Fri, 11/21/2008 - 10:37

jiontro

and how can i do this? can be done inside my bind? pls tell me how!

ioan

#7 Sun, 06/07/2009 - 07:32

jiontro

my bind is settled like:
<div class='quote'>/etc/bind/named.conf:</div>
<div class='quote'>
include "/etc/bind/named.conf.options";

// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
type master;
file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};

// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };

// From the release notes:
// Because many of our users are uncomfortable receiving undelegated answers
// from root or top level domains, other than a few for whom that behaviour
// has been trusted and expected for quite some length of time, we have now
// introduced the "root-delegations-only" feature which applies delegation-only
// logic to all top level domains, and to the root domain. An exception list
// should be specified, including "MUSEUM" and "DE", and any other top level
// domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };

include "/etc/bind/named.conf.local";
</div>

and the <div class='quote'>/etc/bind/named.conf.local :</div>
<div class='quote'>
zone "172.208.77.82.in-addr.arpa" {
type delegation-only;
};
zone "maveion.barlad.rdsnet.ro" {
type delegation-only;
};
zone "jiontro.net" {
type master;
file "/etc/bind/jiontro.net.hosts";
allow-transfer {
127.0.0.1;
localnets;
};
};
zone "1.0.168.192.in-addr.arpa" {
type delegation-only;
};
</div>

Topic locked