Had to think for a moment on how we got our own TLD to work
The answer is that all our resolvers, including the localhost resolvers
for machines in 10.x.x.x space.
Don't recall if it was related to this or not...but these localhost
resolvers also use "forward first;"
I had at one time tried
Either set up a *root* zone, with a delegation to your TLD, and those
other nameservers will be configured with "hints" files
or
You'll have to use some other mechanism -- e.g. slave, stub -- on those
nameservers, so that they know how to resolve names in your TLD.
- Kevin
O
I finally managed to configure a TLD DNS server which will answer, in
its own CLI, with proper IP:s for added domains. The problem is that it
doesn't reply to the other querying Domain DNS servers when they are
asking for domain lookups to it. I can only do lookups inside the TLD
DNS server.
In message <53216b43.8040...@gmail.com>, Peter writes:
> Hi Kevin,
>
> Thanks for your reply. It's just for a closed internal network with no
> access to the rest of the internet. Making labs such as testing ISP
> functions and services, mail servers etc. Everything is running inside
> an VMwa
Hi Kevin,
Thanks for your reply. It's just for a closed internal network with no
access to the rest of the internet. Making labs such as testing ISP
functions and services, mail servers etc. Everything is running inside
an VMware host with an internal closed network.
I have created a closed
5 matches
Mail list logo
