RE: What is wrong with my second $ORIGIN

Just as a general piece of advice, if you're trying to troubleshoot a zonefile parsing issue, sometimes it's useful to just do a zone transfer of the loaded zone and eyeball it. This is obviously more practical with a smaller zone (such as the one you showed) than a huge one, but even if the

Re: Is there a need for clients to advertize the capabilities for DNS Responses over TCP

On Fri, Sep 15, 2017 at 3:37 AM, Harshith Mulky wrote: > Hello Experts, > > > I had a query on advertising the payload size on client in DNS Responses > over UDP/TCP > > > This is as much I have understood from RFC 6891, that a requester(client) > can address his

Re: Is there a need for clients to advertize the capabilities for DNS Responses over TCP

Am 15.09.2017 um 09:37 schrieb Harshith Mulky: Hello Experts, I had a query on advertising the payload size on client in DNS Responses over UDP/TCP This is as much I have understood from RFC 6891, that a requester(client) can address his capabilities to restrict the UDP Payload size to a

Re: What is wrong with my second $ORIGIN

Than you All. Did not notice I had missed a trailing '.' Will make sure I do not miss these things the next time I test -- Sent from: http://bind-users-forum.2342410.n4.nabble.com/ ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users

Is there a need for clients to advertize the capabilities for DNS Responses over TCP

Hello Experts, I had a query on advertising the payload size on client in DNS Responses over UDP/TCP This is as much I have understood from RFC 6891, that a requester(client) can address his capabilities to restrict the UDP Payload size to a limit between 512 to 4096 bytes based on his