At 04:46 13-12-2011, babu dheen wrote:
In what situation, DNS packet size can exceed more than 512
bytes. In fact, my gateway
DNS TXT records used for DKIM, for example.
Regards,
-sm
___
Please visit https://lists.isc.org/mailman/listinfo/bind-us
> Does the resolver of Bind 9 and up use any kind of precaching of resource
> records by default? For instance, does the Bind resolver requery a resource
> record at an authoritative name server before the cache registry for that
> particular resource record expires (i.e., at a time < TTL)? If it d
Hi,
Does the resolver of Bind 9 and up use any kind of precaching of resource
records by default? For instance, does the Bind resolver requery a resource
record at an authoritative name server before the cache registry for that
particular resource record expires (i.e., at a time < TTL)? If it d
On 12/13/2011 07:46 AM, babu dheen wrote:
Dear Anand,
In what situation, DNS packet size can exceed more than 512 bytes. In
fact, my gateway DNS server should not contact internal DNS server
except internal domain name resolution if any user access any internal
website through proxy.
My proxy
On 13/12/11 12:46, babu dheen wrote:
Dear Anand,
In what situation, DNS packet size can exceed more than 512 bytes. In
This has been discussed many times in the list and elsewhere. There's no
need to re-iterate it again.
DNS packets >512 bytes are legal. You should permit them.
In this cas
Dear Anand,
In what situation, DNS packet size can exceed more than 512 bytes. In fact, my
gateway DNS server should not contact internal DNS server except internal
domain name resolution if any user access any internal website through proxy.
My proxy is using gateway DNS for name resolutio
On 13/12/2011 13:04, babu dheen wrote:
> Hi,
>
> Our company users are using internal DNS servers for name resolution
> and internal DNS servers are configured to forward the DNS query to
> company gateway DNS servers for external queries
>
> User --> internal DNS server ---> gateway DNS server
Hi,
Our company users are using internal DNS servers for name resolution and
internal DNS servers are configured to forward the DNS query to company gateway
DNS servers for external queries
User --> internal DNS server ---> gateway DNS server ---> internet
But when i look at the fire
Actually, there's a simpler solution to meeting the rule for 2 NS.
Use any of the secondary nameserver services. The come in a range of
prices/service levels. (Price and delivered service don't always
correlate.) Generally they act as slaves off your master; some are bind
based and use IXFR; ot
It does not seem clear to me if you mix the internal network and the
external network with regards to the 2 server requirement. Everything
inside your own NAT is your own responsibility - you can use any number
of DNS servers you like - 0, 1, 10, n.
For the rest of the world to see, two servers ar
On Tue, Dec 13, 2011 at 3:53 PM, wrote:
>> > For instance, would this be a problem when implementing a
>> > wide area bonjour subdomain using my own local dns server for clients that
>> > are
>> > mobile (internal/external) ?
>>
>> Bonjour should work even without a DNS server.
>
> Reminds me of
>
> What IS the problem, exactly? You're describing two things that
> doesn't seem to be related: number of NS for a zone, and PTR/DNAME
> records.
My appologies if in an attempt to be succint, I failed to be clear.
>
> If you don't "own" an IP address, then usually you don't need to
> bother a
12 matches
Mail list logo