The other way around this is to have the nameservers for the domain
to be in an already resolving domain, that way you dont need to worry
about glue. This is very common.
I had already used the second trick earlier today (after posting the
message) and what I did is pointed a "dead" dom
Vincent Hoffman wrote:
On 11/4/09 21:56, Aryeh M. Friedman wrote:
I have 3 domains that are registered with no-ip.com
(istudentunion.com, org and net). All three are also using their
"no-ip plus" service which provides both static and dynamic resolution
via their nameservers. When I confi
On 11/4/09 21:56, Aryeh M. Friedman wrote:
> I have 3 domains that are registered with no-ip.com
> (istudentunion.com, org and net). All three are also using their
> "no-ip plus" service which provides both static and dynamic resolution
> via their nameservers. When I configure the domains name
Aryeh M. Friedman wrote:
I have 3 domains that are registered with no-ip.com
(istudentunion.com, org and net). All three are also using their
"no-ip plus" service which provides both static and dynamic resolution
via their nameservers. When I configure the domains nameservers to
be theirs
I have 3 domains that are registered with no-ip.com (istudentunion.com,
org and net). All three are also using their "no-ip plus" service which
provides both static and dynamic resolution via their nameservers.
When I configure the domains nameservers to be theirs everything works
great (fo
5 matches
Mail list logo
