BIND - multiple subdomains : 2 simple questions

Hello,

I'm happily using BIND as authorative DNS for my domain soundscript.com, but now I want to create dozens of subdomains. I want to verify how; I have searched and read, but am not confident. For now, all subdomains will be served from the same box, on the same IP.

1st question :

So my current setup is exactly as per SilentRage's "Setting up BIND" guide, in it's simplest form. My soundscript.com.zone therefore includes the line :

www A 69.194.39.28 (my public IP addy)

Am I right in adding the following :

* A 69.194.39.28

To cover all subdomains? I am already on top of adding virtual named hosts for each subdomain to my Apache setup.

2nd question :

Do I need to do anything more or different to the following to get BIND to make this change known to the world? :

I have incremented the serial number in soundscript.com.zone, restarted BIND, and in my named.conf file I have the line :

notify yes;

Is this what automates the "announcement" of zone changes? If not, how is it done?

Many thanks in advance.

My details :
Domain - soundscript.com
System - CPU 800MHz AMD, 512MB RAM
OS - Windows 2000 Pro SP4
Server - Apache 2.0.49
Primary DNS - BIND 9.2.3
Secondary DNS - twisted4life.com
ISP - rogers.com in Canada
Registrar - Network Solutions
Connection - 3mbit cable
Router - Gnet IP0006

yep, the wildcard record looks fine, and using notify yes is fine as well. That's default. It sends notifies to the servers listed in your NS records, so it's important that they are accurate.

Many thanks once again for your continuing excellent help in these forums.

As of yet, I can't reach any subdomains, but I assume I need to wait up to 72 hours.

nah, looks like we've got a problem.

dig soundscript.com

Server Failure. That usually means there's a syntax error in your zone file. Bust out some error information and fix the problem or show it to me.

Beautiful! named-checkzone did it's job and told me "unexpected end of input". Turns out that the zone file needs a new line at the end. Having put that in, all is well.

Is this normal in your experience?

Thanks again.

well, I thought not having a line terminator at the end of the file is only a warnable offense and doesn't break your domain, but it appears to be working fine now.