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 showing too much commitment when it comes to
> DHCPv6 support on Android.
> 
> Android issue tracker  "Support for DHCPv6 (RFC 3315)
> https://issuetracker.google.com/issues/36949085";

While I don't agree with Lorenzo here, 99% of IPv6 networks won't
end up using DHCPv6 for address assignment.  Home networks won't
as they will all use SLAAC, these are, by far, the most numerous
type of network on the planet with hosts on them.  Most business
networks won't as SLAAC meets their needs.

Where DHCPv6 is needed is for prefix delegation.

I also believe there are 3rd party DHCPv6 clients for Android if
you really require them.

Mark

> > I'll be they would if they had Google's level of cash flow.
> >
> 
> 
> --A5C793F7F9B3E7D284FAE4DF
> Content-Type: text/html; charset=utf-8
> Content-Transfer-Encoding: 8bit
> 
> 
>   
> 
>   
>   
> 
> On Thursday 15 June 2017 01:06 PM,
>href="mailto:wbr...@e1b.org";>wbr...@e1b.org wrote:
> 
>  cite="mid:offe8a6ac9.f6535ea0-on85258140.005dd50f-85258140.005df...@e1b.org">
>   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  "Support for DHCPv6 (RFC 3315)  class="moz-txt-link-freetext"
> 
> href="https://issuetracker.google.com/issues/36949085";>https://issuetracker.google.com/issues/36949085";
> 
>  cite="mid:offe8a6ac9.f6535ea0-on85258140.005dd50f-85258140.005df...@e1b.org">
>   I'll be they would if they had Google's level of cash flow.
> 
> 
> 
> 
>   
> 
> 
> --A5C793F7F9B3E7D284FAE4DF--
> 
> --===6845827726844335762==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> ___
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
> from this list
> 
> bind-users mailing list
> bind-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
> --===6845827726844335762==--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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 images that they are running today.  IPv6 is so old that
many ISPs are using the 2nd or 3rd headend that supports IPv6.

The place where they may have to spend money is in their provisioning
systems but even there they can get IPv6 capable DHCPv6 servers for
free.  That and a little bit of training.  It doesn't cost heaps
to turn on IPv6.  It just take someone to say "Yes, we are going
to deliver IPv6 to our customers".  To get over the fear do doing
something new.

Unless you or the ISP have cheaped out on the home router, it will
also support IPv6.  The home router sitting on my desk shipped from
the manufacture (Netgear) supporting IPv6 about 5 years ago now.

An ISP doesn't need a big cash flow to turn on IPv6.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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  "Support for DHCPv6 (RFC 3315)
https://issuetracker.google.com/issues/36949085";
> I'll be they would if they had Google's level of cash flow.
>

___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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 information, and is intended only for the individual or entity 
identified above as the addressee. If you are not the addressee (or the 
employee or agent responsible to deliver it to the addressee), or if this 
message has been addressed to you in error, you are hereby notified that 
you may not copy, forward, disclose or use any part of this message or any 
attachments. Please notify the sender immediately by return e-mail or 
telephone and delete this message from your system.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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  example.com
>>  +short
>> ns1.example.com . hostmaster.example.com
>> . 2017061505 10800 3600 360 3600
>>
>> dig +notcp soa @ns.example.com  example.com
>>  +short
>> ns1.example.com . hostmaster.example.com
>> . 2017061506 10800 3600 360 3600
>>
>> any idea?
>
> Twelve.
>
>
Actually, 1.

$echo "2017061506 - 2017061505" | bc -l
1
$



> ___
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
> from this list
>
> bind-users mailing list
> bind-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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 . hostmaster.example.com
> . 2017061505 10800 3600 360 3600
> 
> dig +notcp soa @ns.example.com  example.com
>  +short
> ns1.example.com . hostmaster.example.com
> . 2017061506 10800 3600 360 3600
> 
> any idea?

Twelve.



signature.asc
Description: OpenPGP digital signature
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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 . hostmaster.example.com 
. 2017061505 10800 3600 360 3600


dig +notcp soa @ns.example.com  example.com 
 +short
ns1.example.com . hostmaster.example.com 
. 2017061506 10800 3600 360 3600


any idea?


what is the purpose to hide anyways public informations especially when 
you seek help from others?


http://www.catb.org/esr/faqs/smart-questions.html#beprecise
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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. Moderate becoming slight
later. Fog patches at first. Good, occasionally very poor at first.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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 360 3600
> 
> dig +notcp soa @ns.example.com example.com +short
> ns1.example.com. hostmaster.example.com. 2017061506 10800 3600 360 3600

Perhaps the zone got updated between your queries.

Have you (as one should in a proper experiment) repeated these queries
to demonstrate that this is happening consistently?

If it is happening consistently, then it's possible that you have *two*
DNS servers listening on the server, one on the UDP socket, and another
on the TCP socket, and they're loaded with different zones.

Regards,
Anand
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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 +short
ns1.example.com. hostmaster.example.com. 2017061506 10800 3600 360 3600

any idea?

thanks,

--
arun
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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 broken --with-gssapi build.

Tony.
-- 
f.anthony.n.finchhttp://dotat.at/  -  I xn--zr8h punycode
Southeast Fitzroy: Northerly or northeasterly 5 to 7, perhaps gale 8 later.
Moderate or rough. Fair. Good.___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users