Screwy Resolver

[react]

Getting e-mails left and right about changing to this new resolver. All the while that resolver is broken and causing all sorts of issues. Support is unresponsive (ticket #HKU-60487-641). Anyone else seeing this?

root@vps log]# nslookup www.slashdot.org (http://www.slashdot.org) 205.234.103.204
Server: 205.234.103.204
Address: 205.234.103.204#53

Non-authoritative answer:
*** Can't find www.slashdot.org: (http://www.slashdot.org:) No answer

root@vps log]# nslookup www.powervps.com (http://www.powervps.com) 205.234.103.204
Server: 205.234.103.204
Address: 205.234.103.204#53

Non-authoritative answer:
*** Can't find www.powervps.com: (http://www.powervps.com:) No answer

[airoid]

Yes, I was unable to send out most e-mail for over 4 hours. Then I received the resolver change notice and knew exactly what was wrong. I opened a new ticket with urgent and they fixed it within minutes.

[react]

In this case I'm using the new resolver but for whatever reason am having problems with it handing back odd responses.

Support have implemented a workaround and expect resolution tomorrow.

[react]

All fixed.

[Fred]

Can you tell us what was the problem ?

thanks :)

[react]

I don't have any details about what was fixed but it was definitely something with the resolving DNS server itself.

[Fred]

okay... I had the same trouble one or two weeks ago. That's why i asked :)

I solved the trouble by adding in resolv.conf the ip of another of my vps ( The one where i host my master dns ) ... Resolution was working from there ... I didn't had the time to investigate... or contact support@ about it...

So, with your post, now i believe the problem was in the config of the new dns server... The configuration section where they put the IP allowed to resolve and stuff... I mean, the "allow-*" configuration in the named.conf ...

Maybe, some IP ranges weren't in the config so we were not allowed ? :)