What he is saying is that your registrar now knows the location of the name servers that are authoritative for the "fake.com" zone. Now you have to create A records for your server name to be correctly resolved when someone types "www.fake.com" into their browser. On your BIND server you would create some entries in the SOA zone file for fake.com. Maybe like this:
fake.com IN A xxx.xxx.xxx.xxx (x's being your IP)
www.fake.com IN A xxx.xxx.xxx.xxx (probably same IP)
Then there are MX records etc. If you want to host your own DNS, that is a laudable goal, but keeping up with security and the fact that crackers love nothing better than attacking BIND servers, you might just sign up for something like Verisigns advanced DNS management. You simply create your host, MX, Cname whatever records and they manage and propagate them for you. That is cheap at $24 per domain. Good luck.