From here, it says : Ninject doesn't have XML configuration.
Free yourself from XML
Most other .NET dependency injection frameworks are designed around the use of XML to declare type bindings. Rather than forcing you to write cumbersome and error-prone text, Ninject arms you with a fluent interface, which lets you connect the pieces of your application using full-fledged code. This means you can take advantage of the features of the IDE and compiler, like code completion and type-safety.
There's been a general trend (among the folks I know or follow, anyway) to moving IoC bindings into code and out of XML. Mostly b/c you gain intellisense and runtime feedback of screw-ups.
I haven't used it but there are release candidates for Ninject.Extensions.Xml which allows you to setup your mappings in xml. However I would generally shy away from doing it this way. There's also Ninject.Extensions.Conventions which might be what you're after.
Source :
Ninject and configuration
Ninject and XML configuration Binding