From: Dave Presotto presotto@plan9.bell-labs.com
Subject: Can't get dns to work
Date: Mon, 4 Mar 1996 10:50:17 -0500 [thread overview]
Message-ID: <19960304155017.CquOB-3lfULF7j2tHHuRbEyfkZIi3e4juV3ywGWLB5E@z> (raw)
at the very least...
#
# external internet domain service
#
dom=
ns=A.ROOT-SERVERS.NET
ns=B.ROOT-SERVERS.NET
ns=C.ROOT-SERVERS.NET
ns=D.ROOT-SERVERS.NET
ns=E.ROOT-SERVERS.NET
ns=F.ROOT-SERVERS.NET
ns=G.ROOT-SERVERS.NET
ns=H.ROOT-SERVERS.NET
ns=I.ROOT-SERVERS.NET
dom=A.ROOT-SERVERS.NET ip=198.41.0.4
dom=B.ROOT-SERVERS.NET ip=128.9.0.107
dom=C.ROOT-SERVERS.NET ip=192.33.4.12
dom=D.ROOT-SERVERS.NET ip=128.8.10.90
dom=E.ROOT-SERVERS.NET ip=192.203.230.10
dom=F.ROOT-SERVERS.NET ip=192.5.5.241 ip=39.13.229.241
dom=G.ROOT-SERVERS.NET ip=192.112.36.4
dom=H.ROOT-SERVERS.NET ip=128.63.2.53
dom=I.ROOT-SERVERS.NET ip=192.36.148.17
If you would rather a different name server for the root,
use this instead
dom=
ns=ns1.infinet.com
ns=ns2.infinet.com
dom=ns1.infinet.com ip=206.103.240.1
dom=ns2.infinet.com ip=206.103.240.2
If you'ld still like to point to the real root servers but
point to infinet.com's server for infinet domain names:
dom=
ns=A.ROOT-SERVERS.NET
ns=B.ROOT-SERVERS.NET
ns=C.ROOT-SERVERS.NET
ns=D.ROOT-SERVERS.NET
ns=E.ROOT-SERVERS.NET
ns=F.ROOT-SERVERS.NET
ns=G.ROOT-SERVERS.NET
ns=H.ROOT-SERVERS.NET
ns=I.ROOT-SERVERS.NET
dom=A.ROOT-SERVERS.NET ip=198.41.0.4
dom=B.ROOT-SERVERS.NET ip=128.9.0.107
dom=C.ROOT-SERVERS.NET ip=192.33.4.12
dom=D.ROOT-SERVERS.NET ip=128.8.10.90
dom=E.ROOT-SERVERS.NET ip=192.203.230.10
dom=F.ROOT-SERVERS.NET ip=192.5.5.241 ip=39.13.229.241
dom=G.ROOT-SERVERS.NET ip=192.112.36.4
dom=H.ROOT-SERVERS.NET ip=128.63.2.53
dom=I.ROOT-SERVERS.NET ip=192.36.148.17
dom=infinet.com
ns=ns1.infinet.com
ns=ns2.infinet.com
dom=ns1.infinet.com ip=206.103.240.1
dom=ns2.infinet.com ip=206.103.240.2
Pointers to domain name servers are of the form:
dom=yyy.zzz
ns=xxx1
ns=xxx2
ns=xxx3
This means that for any name in the name hierarchy that is
at or below yyy.zzz, use the name servers xxx1, xxx2, and xxx3
unless a more specific match is found.
Of course, this is just seeding a cache. If more authoritative
info comes back from a dns name server, it will be used instead.
If you want to be the name server for a domain, then add
a soa= in the tuple. For example, we implement the bell-labs.com
domain and /lib/ndb/local has the following:
#
# external internet domain service
#
dom=
ns=A.ROOT-SERVERS.NET
ns=B.ROOT-SERVERS.NET
ns=C.ROOT-SERVERS.NET
ns=D.ROOT-SERVERS.NET
ns=E.ROOT-SERVERS.NET
ns=F.ROOT-SERVERS.NET
ns=G.ROOT-SERVERS.NET
ns=H.ROOT-SERVERS.NET
ns=I.ROOT-SERVERS.NET
dom=A.ROOT-SERVERS.NET ip=198.41.0.4
dom=B.ROOT-SERVERS.NET ip=128.9.0.107
dom=C.ROOT-SERVERS.NET ip=192.33.4.12
dom=D.ROOT-SERVERS.NET ip=128.8.10.90
dom=E.ROOT-SERVERS.NET ip=192.203.230.10
dom=F.ROOT-SERVERS.NET ip=192.5.5.241 ip=39.13.229.241
dom=G.ROOT-SERVERS.NET ip=192.112.36.4
dom=H.ROOT-SERVERS.NET ip=128.63.2.53
dom=I.ROOT-SERVERS.NET ip=192.36.148.17
#
# lucent name servers
#
dom=bell-labs.com soa=
ns=ns.research.att.com
ns=achille.research.att.com
ns=castro.bell-labs.com
ns=divisadero.bell-labs.com
mx=divisadero.bell-labs.com pref=2
mx=castro.bell-labs.com pref=1
dom=*.bell-labs.com
mx=divisadero.bell-labs.com pref=2
mx=castro.bell-labs.com pref=1
Cheers...
next reply other threads:[~1996-03-04 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-04 15:50 Dave [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-03-03 19:08 Luther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19960304155017.CquOB-3lfULF7j2tHHuRbEyfkZIi3e4juV3ywGWLB5E@z \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).