setting up local authorative name server with a no-ip.com registered domain

[Vincent Hoffman]

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 nameservers to
> be theirs everything works great (for the most part), but when I
> change the nameservers to my own sites BIND (base 7.3-RELEASE) I can
> get everything to resolve locally and via dig/host/nslookup remotely
> (if and only if I specify the nameserver by IP).   What appears to be
> happing is this:
>
> ~/Desktop:aryeh at flosoft% !d
> dig ns istudentunion.org +trace
>
> ; <<>> DiG 9.4.3-P2 <<>> ns istudentunion.org +trace
> ;; global options:  printcmd
> .            463753    IN    NS    I.ROOT-SERVERS.NET.
> .            463753    IN    NS    C.ROOT-SERVERS.NET.
> .            463753    IN    NS    L.ROOT-SERVERS.NET.
> .            463753    IN    NS    K.ROOT-SERVERS.NET.
> .            463753    IN    NS    M.ROOT-SERVERS.NET.
> .            463753    IN    NS    A.ROOT-SERVERS.NET.
> .            463753    IN    NS    E.ROOT-SERVERS.NET.
> .            463753    IN    NS    B.ROOT-SERVERS.NET.
> .            463753    IN    NS    H.ROOT-SERVERS.NET.
> .            463753    IN    NS    D.ROOT-SERVERS.NET.
> .            463753    IN    NS    G.ROOT-SERVERS.NET.
> .            463753    IN    NS    F.ROOT-SERVERS.NET.
> .            463753    IN    NS    J.ROOT-SERVERS.NET.
> ;; Received 500 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms
>
> org.            172800    IN    NS    B2.ORG.AFILIAS-NST.org.
> org.            172800    IN    NS    A2.ORG.AFILIAS-NST.INFO.
> org.            172800    IN    NS    C0.ORG.AFILIAS-NST.INFO.
> org.            172800    IN    NS    B0.ORG.AFILIAS-NST.org.
> org.            172800    IN    NS    A0.ORG.AFILIAS-NST.INFO.
> org.            172800    IN    NS    D0.ORG.AFILIAS-NST.org.
> ;; Received 437 bytes from 192.203.230.10#53(E.ROOT-SERVERS.NET) in 86 ms
>
> istudentunion.org.    86400    IN    NS    ns2.istudentunion.org.
> istudentunion.org.    86400    IN    NS    ns1.istudentunion.org.
> ;; Received 103 bytes from 199.19.54.1#53(B0.ORG.AFILIAS-NST.org) in
> 88 ms
>
> ;; connection timed out; no servers could be reached
>
Since your nameservers for istudentunion.org are in the
istudentunion.org domain, you will need glue at the parent nameservers
to prevent a chicken and egg problem.
Exactly how you tell no-ip this i'm not sure but its not a terribly
unusual request. Once the have added it you will need to wait for the
.org tld zone to update (not sure of their schedule but better than the
once or twice a day of 10 years ago :)
    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.



Vince


> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to
> "freebsd-hackers-unsubscribe at freebsd.org"