ameserver
>> > but each gives a different IP. Are the results undefined? Is there some
>> > rule
>> > that is followed to resolve the conflict?
>
> On 07.01.09 19:14, Dawn Connelly wrote:
>> Each registrars push the information that they have. So if you have
>&g
Each registrars push the information that they have. So if you have
apples.com with an NS record of ns1.dns.com==137.161.0.1 and
oranges.com with a NS record of ns1.dns.com=137.161.0.2, when people
query for apples, they will get the .1 address and when they query for
oranges.com they will get the
You can make a single generic file and reference that one file repeatedly in
the named.conf in each zone definition. I do that frequently for private IP
address space. But keep in mind that if there are any errors in the file,
you loose EVERYTHING. You can also consider using "INCLUDE" statements i
Looks to me like someone took their laptop home that is configured for your
active directory domain and the laptop is trying to call home. I use to see
that all the time. I'm guessing that your AD domain and the domain that they
are querying are the same?
On Fri, Dec 5, 2008 at 1:17 PM, Keve Nagy
Hey, maybe it's time to agree to disagree on this one? If Bert and Ernie can
live together in roommate bliss, I'm sure we can all accept and appreciate
each others differences.
On Mon, Nov 17, 2008 at 7:47 PM, Kevin Darcy <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>
>> Just because ind
You have recursion set to no. So the only thing the DNS server will answer
for is zones it is authoritative for. If you want to use it as a DNS server
for clients, you need to allow recursionfor an ACL that has the IP address
space that your clients are coming from. Here's an example:
acl "trusted
6 matches
Mail list logo
