Re: make AAAA type the default for dig

2017-06-15 Thread Mark Andrews
In message <22408832-7b45-c1dc-870d-c16fb8cb9...@gmail.com>, Sachin Garg writes: > > On Thursday 15 June 2017 01:06 PM, wbr...@e1b.org wrote: > > Mark Andrews wrote on 06/15/2017 12:02:37 AM: > > > >> Other ISP's should try to match Google's level of IPv6 commitment. > They don't seem to be showi

Re: make AAAA type the default for dig

2017-06-15 Thread Mark Andrews
In message , wbr...@e1b.org writes: > Mark Andrews wrote on 06/15/2017 12:02:37 AM: > > > Other ISP's should try to match Google's level of IPv6 commitment. > > I'll be they would if they had Google's level of cash flow. Most ISP's already have hardware that supports IPv6. Its in the software

Re: make AAAA type the default for dig

2017-06-15 Thread Sachin Garg
On Thursday 15 June 2017 01:06 PM, wbr...@e1b.org wrote: > Mark Andrews wrote on 06/15/2017 12:02:37 AM: > >> Other ISP's should try to match Google's level of IPv6 commitment. They don't seem to be showing too much commitment when it comes to DHCPv6 support on Android. Android issue tracker "Su

Re: make AAAA type the default for dig

2017-06-15 Thread wbrown
Mark Andrews wrote on 06/15/2017 12:02:37 AM: > Other ISP's should try to match Google's level of IPv6 commitment. I'll be they would if they had Google's level of cash flow. Confidentiality Notice: This electronic message and any attachments may contain confidential or privileged informatio

Re: difference in responses between UDP and TCP

2017-06-15 Thread Warren Kumari
On Thu, Jun 15, 2017 at 11:13 AM, Alan Clegg wrote: > > > On 6/15/17 6:20 AM, Arun Natarajan wrote: >> Hello, >> >> Wondering why we are seeing different serial numbers from a bind >> authoritative server for requests over UDP and TCP. >> >> dig +tcp soa @ns.example.com exa

Re: difference in responses between UDP and TCP

2017-06-15 Thread Alan Clegg
On 6/15/17 6:20 AM, Arun Natarajan wrote: > Hello, > > Wondering why we are seeing different serial numbers from a bind > authoritative server for requests over UDP and TCP. > > dig +tcp soa @ns.example.com example.com > +short > ns1.example.com

Re: difference in responses between UDP and TCP

2017-06-15 Thread Reindl Harald
Am 15.06.2017 um 12:20 schrieb Arun Natarajan: Hello, Wondering why we are seeing different serial numbers from a bind authoritative server for requests over UDP and TCP. dig +tcp soa @ns.example.com example.com +short ns1.example.com

Re: difference in responses between UDP and TCP

2017-06-15 Thread Tony Finch
Arun Natarajan wrote: > > any idea? Without knowing the server host name and zone name there could be lots of different reasons, so there isn't really any way to answer. Tony. -- f.anthony.n.finchhttp://dotat.at/ - I xn--zr8h punycode Dover: Southwest 5 to 7, veering west 4 or 5 later. Mo

Re: difference in responses between UDP and TCP

2017-06-15 Thread Anand Buddhdev
On 15/06/2017 12:20, Arun Natarajan wrote: > Hello, > > Wondering why we are seeing different serial numbers from a bind > authoritative server for requests over UDP and TCP. > > dig +tcp soa @ns.example.com example.com +short > ns1.example.com. hostmaster.example.com. 2017061505 10800 3600 3600

difference in responses between UDP and TCP

2017-06-15 Thread Arun Natarajan
Hello, Wondering why we are seeing different serial numbers from a bind authoritative server for requests over UDP and TCP. dig +tcp soa @ns.example.com example.com +short ns1.example.com. hostmaster.example.com. 2017061505 10800 3600 360 3600 dig +notcp soa @ns.example.com example.com +shor

Re: BIND 9.11.x build failing on Mac OS X - gssapi errors

2017-06-15 Thread Tony Finch
James Brown via bind-users wrote: > > If I use: > > ./configure --with-atf —without-gssapi > > I get it failing with: > > Undefined symbols for architecture x86_64: > "_gss_accept_sec_context", referenced from: Looks like you need to `make clean` to get rid of old build artefacts from the broke