DNS FlagDay bind version affected

Mark Andrews marka at isc.org
Mon Jan 28 20:03:52 UTC 2019


Everyone please remember that no one can give you accurate answers without knowing the ACTUAL details. Both FIREWALL and NAMESERVER need to be tested TOGETHER.

Well if it is this set of servers below you either have a routing issue or a firewall which is blocking all DNS queries to 186.154.147.2 assuming that 2001:470:4:41e::2 and 186.154.147.2 are actually the same machine.

ignios.net. @198.199.105.222 (ns.02.ignios.net.): dns=ok edns=ok edns1=ok edns at 512=ok ednsopt=ok edns1opt=ok do=ok ednsflags=ok optlist=ok,expire,cookie,subnet signed=ok ednstcp=ok bind11=ok,cookie+badcookie
ignios.net. @2604:a880:1:20::2:6001 (ns.02.ignios.net.): dns=ok edns=ok edns1=ok edns at 512=ok ednsopt=ok edns1opt=ok do=ok ednsflags=ok optlist=ok,expire,cookie,subnet signed=ok ednstcp=ok bind11=ok,cookie+badcookie
ignios.net. @190.85.201.42 (ns.01.ignios.net.): dns=ok edns=ok edns1=ok edns at 512=ok ednsopt=ok edns1opt=ok do=ok ednsflags=ok optlist=ok,expire,cookie,subnet signed=ok ednstcp=ok bind11=ok,cookie
ignios.net. @2a03:b0c0:3:d0::26:2001 (ns.03.ignios.net.): dns=ok edns=ok edns1=ok edns at 512=ok ednsopt=ok edns1opt=ok do=ok ednsflags=ok optlist=ok,expire,cookie,subnet signed=ok ednstcp=ok bind11=ok,cookie
ignios.net. @165.227.162.5 (ns.03.ignios.net.): dns=ok edns=ok edns1=ok edns at 512=ok ednsopt=ok edns1opt=ok do=ok ednsflags=ok optlist=ok,expire,cookie,subnet signed=ok ednstcp=ok bind11=ok,cookie
ignios.net. @2400:6180:0:d0::94:5001 (ns.04.ignios.net.): dns=ok edns=ok edns1=ok edns at 512=ok ednsopt=ok edns1opt=ok do=ok ednsflags=ok optlist=ok,cookie+badcookie,subnet signed=ok ednstcp=ok bind11=ok,cookie
ignios.net. @139.59.127.149 (ns.04.ignios.net.): dns=ok edns=ok edns1=ok edns at 512=ok ednsopt=ok edns1opt=ok do=ok ednsflags=ok optlist=ok,cookie+badcookie,subnet signed=ok ednstcp=ok bind11=ok,cookie
ignios.net. @2001:470:4:41e::2 (ns.01.ignios.net.): dns=ok edns=ok edns1=ok edns at 512=ok ednsopt=ok edns1opt=ok do=ok ednsflags=ok optlist=ok,expire,cookie,subnet signed=ok ednstcp=ok bind11=ok,cookie
ignios.net. @186.154.147.2 (ns.01.ignios.net.): dns=timeout edns=timeout edns1=timeout edns at 512=timeout ednsopt=timeout edns1opt=timeout do=timeout ednsflags=timeout optlist=timeout signed=timeout ednstcp=timeout bind11=timeout

Mark


> On 29 Jan 2019, at 4:46 am, German Molano <gmolano at ignios.net> wrote:
> 
> Hi to all.
> 
> Checking on the website (https://dnsflagday.net/)  my domains are affected by the EDNS compliance update. I use the RMPs provided by 510 SG (https://www.five-ten-sg.com/mapper/bind) The last version is Bind 9.12.3-P1 this version is ok? Or there is something else that i have to fix on the current setup?
> 
> 
> Atentamente. 
> 
> German Molano 
> IgniOS Corp. 
> Cel: +57-3005706799 
> PBX: +57-8-2762624 
> Skype: ignios.corp
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka at isc.org



More information about the bind-users mailing list