Re: FORMERR

The SOA record in the negative response didn't match the delegation. cloudfront.net != stl2.cloudfront.net Mark In message , "Jeremy C. Reed" writes: > The upcoming BIND 9.7.0 has several logging improvements, for example: > > 04-Dec-2009 14:46:41.020 resolver: notice: DNS format err

Re: FORMERR

The upcoming BIND 9.7.0 has several logging improvements, for example: 04-Dec-2009 14:46:41.020 resolver: notice: DNS format error from 216.137.38.22#53 resolving d2rdfnizen5apl.stl2.cloudfront.net/ for client 127.0.0.1#53764: invalid response 04-Dec-2009 14:46:41.060 resolver: notice: DNS

FORMERR

Occasionally I will look the "lame-log" on one of my BIND 9.6.1-P1 servers and find FORMERR messages. Then I do DNS queries to try to understand why the FORMERR occurred. Here is one where I am confused: 03-Dec-2009 16:07:50.722 lame-servers: info: FORMERR resolving 'd2rdfnizen5apl.stl2.cloud

Re: Punycode & nslookup

On Dec 4, 2009, at 10:12 AM, Joe Baptista wrote: > On Fri, Dec 4, 2009 at 12:26 PM, Chris Buxton wrote: > >> nslookup will only understand IDN if BIND is compiled with that option in >> the ./configure step. > > might be a good idea if it was the default option. as idn becomes popular the >

Re: Punycode & nslookup

Folks, remember when discussing 'nslookup' that there are not only at least three [?] major revisions in the BIND line, but also an identically-named tool on MS Windows. I'm sure the older ones don't support punycode. I wouldn't know about the MSW tool. Maybe not a problem with the specific post

Re: Punycode & nslookup

On Fri, Dec 4, 2009 at 12:26 PM, Chris Buxton wrote: > nslookup will only understand IDN if BIND is compiled with that option in > the ./configure step. > might be a good idea if it was the default option. as idn becomes popular the lack of idn support for the tools will result in confusion. >

Re: Punycode & nslookup

On Dec 4, 2009, at 7:23 AM, Kai Szymanski wrote: > Hi Joe, > > my "problem" is: I can't test the zone with nslookup (only when i use the > puny-encoded domainname). nslookup will only understand IDN if BIND is compiled with that option in the ./configure step. > Also other tools who uses dns t

Re: Punycode & nslookup

On Fri, Dec 4, 2009 at 10:23 AM, Kai Szymanski wrote: > Hi Joe, > > my "problem" is: I can't test the zone with nslookup (only when i use the > puny-encoded domainname). Also other tools who uses dns to resolv the > entered domainname (like ping > www.umlauttestäöü.de

Re: Punycode & nslookup

Hi Joe, my "problem" is: I can't test the zone with nslookup (only when i use the puny-encoded domainname). Also other tools who uses dns to resolv the entered domainname (like ping www.umlauttestäöü.de) did'nt work. So i thought that 1. The User enters a url with Umlauts in browser 2. Brows

Re: Punycode & nslookup

You configure an idn zone the same way you do for any other - so I assume your config below is correct - although the location of the master file master/umlauttestäöü.de.hosts contains non ascii char I don't think that is an issue in todays unix/linux environment. It would of been a problem in the

Punycode & nslookup

Hi! One of our customers wan't a Domain with "Umlaute" (german special characters like "ä"). Is it correct when i have configured the zone like zone "xn--umlauttest-z5a0tyc.de" { type master; file "master/umlauttestäöü.de.hosts"; allow-transfer { can_transfer; }; #

Re: Disable Refused answer

On Dec 3 2009, Bill Larson wrote: [...] Then again, I've never been sure what the original requester was asking for. If he didn't want to give an answer out to someone on a particular network, then the "blackhole" option would seem to be a perfect solution in the first place. | blackhole |

Bind 9.4.3-P3 on Solaris 10 Hang

Hi, recently we've had a number of incidents where named has stopped answering requests and is spinning the CPU. The only symptom we have been able find is that there are lots and lots of open sockets. We've been unable to find anything logged that would suggest that there is an issue. Has a