You have to read .help +host and see the syntax for it because you were using it incorectly.
Keep in mind that it is a hostMASK which implies that it can be a hostname masked by special chars in order to allow less strict variations. Hence, you can have * as a nickname mask and use something of the sort:
.+host <your handle> *!
mattyp@ACAFE3F8.ipt.aol.com
Also, since (afaik) aol varies even the hostnames and not only the IP of the user, you might want to consider masking the part of ACAFE3F8 to something like ACAFE* so to allow for minor changes in your hostname. I don't really have a clue about internal working of AOL.com but you could start tracking your hostname for a few days and see if there is a common ellement between different hosts if yours (if it differs at all).
Another issue with dynamic hosts/IPs is that you are sort of forced to use very loose hostmasks like *!mattyp@*.ipt.aol.com which might have bot confuse you with someone else and allow that person certain access to commands that don't require authentication, or it can even screw up attempts to ban certain user (other than yourself) ect.. So advice would be to:
1) Come up with a hostmask that matches your real n!u@host as close as possible. Like setting your nick as part of it: Mathew!
mattyp@ACAFE3F8.ipt.aol.com
2) Do not run any of lame scripts that don't ask for authentication. Eggdrop itself doesn't have such problem security holes, but plenty of custom TCL scripts do.
3) Finaly, if you ever use /msg bot ident pass handle, make sure to .whois yourself and remove the hostmask in case it was added in a form that might compromise security.
Ignorant and lazy people will save 30 minutes by chosing simple config file. Smart ones will save 3000 minutes of *everyone's* time by opting for complete config file.